Difference between revisions of "INCONSISTENT DATA"
Jump to navigation
Jump to search
m (Topic titles in capital letters) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | <div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[Main Page]] / Back to [Design Issues]] / Back to [Test Automation Issues]]</span><br /> | + | <div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Design Issues]] / Back to [[Test Automation Issues]]</span><br /> |
=<span style="font-size: 16px">'''Issue summary'''</span>= | =<span style="font-size: 16px">'''Issue summary'''</span>= | ||
<span style="font-size: 16px">The data needed for the automated test cases changes unpredictably</span> | <span style="font-size: 16px">The data needed for the automated test cases changes unpredictably</span> | ||
| Line 5: | Line 5: | ||
<span style="font-size: 16px">Design</span> | <span style="font-size: 16px">Design</span> | ||
=<span style="font-size: 16px">'''Examples'''</span>= | =<span style="font-size: 16px">'''Examples'''</span>= | ||
| − | * <span style="font-size: 16px">Test data is obtained by anonymising customer data. This has some major disadvantages:<br /> - The data must by anonymised (this can be tricky)<br /> - You must be able to use different IDs or search criteria for every run<br /> - you probably | + | * <span style="font-size: 16px">Test data is obtained by anonymising customer data. This has some major disadvantages:<br /> - The data must by anonymised (this can be tricky)<br /> - You must be able to use different IDs or search criteria for every run<br /> - you probably won't get just the data combination that you need for a special test case and if you add it, it will be overwritten next time you get a new batch of customer data<br /> - different input data means different output data, so it will be more difficult to compare results</span> |
* <span style="font-size: 16px">Test automation shares databases with testing or development</span> | * <span style="font-size: 16px">Test automation shares databases with testing or development</span> | ||
* <span style="font-size: 16px">After an update to the Software Under Test (SUT) the data is not compatible any longer</span> | * <span style="font-size: 16px">After an update to the Software Under Test (SUT) the data is not compatible any longer</span> | ||
| Line 14: | Line 14: | ||
<span style="font-size: 16px"> Most recommended:</span><br /> | <span style="font-size: 16px"> Most recommended:</span><br /> | ||
* <span style="font-size: 16px">[[FRESH SETUP]] should help you in most cases</span> | * <span style="font-size: 16px">[[FRESH SETUP]] should help you in most cases</span> | ||
| − | * <span style="font-size: 16px; line-height: 1.5">[[ DEDICATED RESOURCES]]: look up this pattern if you have to share resources</span> | + | * <span style="font-size: 16px; line-height: 1.5">[[DEDICATED RESOURCES]]: look up this pattern if you have to share resources</span> |
* <span style="font-size: 16px">[[WHOLE TEAM APPROACH]]: if your team follows an agile development process this is the pattern to use in order to avoid this kind of problems from the beginning</span> | * <span style="font-size: 16px">[[WHOLE TEAM APPROACH]]: if your team follows an agile development process this is the pattern to use in order to avoid this kind of problems from the beginning</span> | ||
<br /> <span style="font-size: 16px">Other useful patterns:</span><br /> | <br /> <span style="font-size: 16px">Other useful patterns:</span><br /> | ||
* <span style="font-size: 16px">[[SHARE INFORMATION]]: use this pattern for better communication between development, testing and automation </span> | * <span style="font-size: 16px">[[SHARE INFORMATION]]: use this pattern for better communication between development, testing and automation </span> | ||
* <span style="font-size: 16px">[[ DESIGN FOR REUSE]]: this pattern should be used always</span> | * <span style="font-size: 16px">[[ DESIGN FOR REUSE]]: this pattern should be used always</span> | ||
| − | <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Design Issues]] / Back to [[Test Automation Issues]] | + | <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Design Issues]] / Back to [[Test Automation Issues]] |
Latest revision as of 16:04, 27 June 2018
.................................................................................................................Main Page / Back to Design Issues / Back to Test Automation Issues
Issue summary
The data needed for the automated test cases changes unpredictably
Category
Design
Examples
- Test data is obtained by anonymising customer data. This has some major disadvantages:
- The data must by anonymised (this can be tricky)
- You must be able to use different IDs or search criteria for every run
- you probably won't get just the data combination that you need for a special test case and if you add it, it will be overwritten next time you get a new batch of customer data
- different input data means different output data, so it will be more difficult to compare results - Test automation shares databases with testing or development
- After an update to the Software Under Test (SUT) the data is not compatible any longer
- Tests alter the data for following tests
Questions
How do you collect the necessary data?
Resolving Patterns
Most recommended:
- FRESH SETUP should help you in most cases
- DEDICATED RESOURCES: look up this pattern if you have to share resources
- WHOLE TEAM APPROACH: if your team follows an agile development process this is the pattern to use in order to avoid this kind of problems from the beginning
Other useful patterns:
- SHARE INFORMATION: use this pattern for better communication between development, testing and automation
- DESIGN FOR REUSE: this pattern should be used always
.................................................................................................................Main Page / Back to Design Issues / Back to Test Automation Issues