Difference between revisions of "TEST DATA LOSS"
Jump to navigation
Jump to search
m (Topic titles in capital letters) |
|||
| Line 1: | Line 1: | ||
<div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Process Issues]] / Back to [[Test Automation Issues]]</span> | <div id="content_view" class="wiki" style="display: block"><span style="font-size: 14px">.................................................................................................................[[Main Page]] / Back to [[Process Issues]] / Back to [[Test Automation Issues]]</span> | ||
| − | =<span style="font-size: 16px">Issue Summary</span>= | + | =<span style="font-size: 16px">'''Issue Summary'''</span>= |
| − | <span style="font-family: Arial; font-size: 16px">Test data isn’t secured so that it has to be generated again and again.</span | + | <span style="font-family: Arial; font-size: 16px">Test data isn’t secured so that it has to be generated again and again.</span> |
| − | =<span style="font-size: 16px">Category</span>= | + | =<span style="font-size: 16px">'''Category'''</span>= |
<span style="font-size: 16px">Process</span><br /> <span style="font-family: Arial; font-size: 16px"> </span> | <span style="font-size: 16px">Process</span><br /> <span style="font-family: Arial; font-size: 16px"> </span> | ||
| − | =<span style="font-family: Arial; font-size: 16px">Examples</span>= | + | =<span style="font-family: Arial; font-size: 16px">'''Examples'''</span>= |
| − | |||
| − | |||
# <span style="font-family: Arial; font-size: 16px">Testers create new data every time because it's too difficult to check if test data is already available.</span> | # <span style="font-family: Arial; font-size: 16px">Testers create new data every time because it's too difficult to check if test data is already available.</span> | ||
# <span style="font-family: Arial; font-size: 16px">Every tester has his own data portfolio and doesn't share it with test automation.</span> | # <span style="font-family: Arial; font-size: 16px">Every tester has his own data portfolio and doesn't share it with test automation.</span> | ||
# <span style="font-family: Arial; font-size: 16px">Anonimized production data is used and it has to be generated anew every time.</span> | # <span style="font-family: Arial; font-size: 16px">Anonimized production data is used and it has to be generated anew every time.</span> | ||
| − | + | =<span style="font-family: Arial; font-size: 16px">'''Questions'''</span>= | |
| − | =<span style="font-family: Arial; font-size: 16px">Questions</span>= | + | <span style="font-family: Arial; font-size: 16px">How is test data structured? Text files? Databases? Other?</span><br /> <span style="font-family: Arial; font-size: 16px">Are there naming and documentation standards?</span><br /> <span style="font-family: Arial; font-size: 16px">Who creates the data? Who uses it?</span> |
| − | <span style="font-family: Arial; font-size: 16px">How is test data structured? Text files? Databases? Other?</span><br /> <span style="font-family: Arial; font-size: 16px">Are there naming and documentation standards?</span><br /> <span style="font-family: Arial; font-size: 16px">Who creates the data? Who uses it?</span | + | =<span style="font-family: Arial; font-size: 16px">'''Resolving Patterns'''</span>= |
| − | =<span style="font-family: Arial; font-size: 16px">Resolving Patterns</span>= | ||
<span style="font-family: Arial; font-size: 16px">Most recommended:</span><br /> | <span style="font-family: Arial; font-size: 16px">Most recommended:</span><br /> | ||
| − | |||
* <span style="font-family: Arial; font-size: 16px">[[ LAZY AUTOMATOR]]: Apply this pattern if you want to resolve the issue once and for all. It contains all the other resolving patterns!</span> | * <span style="font-family: Arial; font-size: 16px">[[ LAZY AUTOMATOR]]: Apply this pattern if you want to resolve the issue once and for all. It contains all the other resolving patterns!</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">[[ 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">[[DON'T REINVENT THE WHEEL]]: use this pattern as often as possible! </span> | * <span style="font-size: 16px">[[DON'T REINVENT THE WHEEL]]: use this pattern as often as possible! </span> | ||
Latest revision as of 09:36, 30 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