Difference between revisions of "TEST DATA LOSS"
Jump to navigation
Jump to search
(Created page with "<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.........................................................................................") |
|||
| Line 20: | Line 20: | ||
* <span style="font-size: 16px">[[ DESIGN FOR REUSE]]: This pattern should have been applied from the very beginning of the automation effort. Still, if you haven't, do it for all new automation projects. Use it also every time you have to refactor something.</span> | * <span style="font-size: 16px">[[ DESIGN FOR REUSE]]: This pattern should have been applied from the very beginning of the automation effort. Still, if you haven't, do it for all new automation projects. Use it also every time you have to refactor something.</span> | ||
| − | * <span style="font-size: 16px">[[ | + | * <span style="font-size: 16px">[[DON'T REINVENT THE WHEEL]]: use this pattern as often as possible! </span> |
* <span style="font-size: 16px">[[GOOD DEVELOPMENT PROCESS]]: Again a pattern that should have been applied from the start. If you didn't, do so now!</span> | * <span style="font-size: 16px">[[GOOD DEVELOPMENT PROCESS]]: Again a pattern that should have been applied from the start. If you didn't, do so now!</span> | ||
* <span style="font-size: 16px">[[GOOD PROGRAMMING PRACTICES]]: same as for [[GOOD DEVELOPMENT PROCESS]]!</span> | * <span style="font-size: 16px">[[GOOD PROGRAMMING PRACTICES]]: same as for [[GOOD DEVELOPMENT PROCESS]]!</span> | ||
<br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Process Issues]] / Back to [[Test Automation Issues]]</span></div> | <br /> <span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Process Issues]] / Back to [[Test Automation Issues]]</span></div> | ||
Revision as of 15:16, 24 April 2018
.................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues
.................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues
Issue Summary
Test data isn’t secured so that it has to be generated again and again.
Category
Process
Examples
- Testers create new data every time because it's too difficult to check if test data is already available.
- Every tester has his own data portfolio and doesn't share it with test automation.
- Anonimized production data is used and it has to be generated anew every time.
Questions
How is test data structured? Text files? Databases? Other?
Are there naming and documentation standards?
Who creates the data? Who uses it?
Resolving Patterns
Most recommended:
- LAZY AUTOMATOR: Apply this pattern if you want to resolve the issue once and for all. It contains all the other resolving patterns!
Other useful patterns:
- DESIGN FOR REUSE: This pattern should have been applied from the very beginning of the automation effort. Still, if you haven't, do it for all new automation projects. Use it also every time you have to refactor something.
- DON'T REINVENT THE WHEEL: use this pattern as often as possible!
- GOOD DEVELOPMENT PROCESS: Again a pattern that should have been applied from the start. If you didn't, do so now!
- GOOD PROGRAMMING PRACTICES: same as for GOOD DEVELOPMENT PROCESS!
.................................................................................................................Main Page / Back to Process Issues / Back to Test Automation Issues