Difference between revisions of "Not reusing existing data"

From Test Automation Patterns
Jump to navigation Jump to search
Line 10: Line 10:
 
# <span style="font-size: 16px">Data has to be updated from release to release</span>
 
# <span style="font-size: 16px">Data has to be updated from release to release</span>
 
<br /> <span style="font-size: 16px">Return to [[Creation or maintenance of test data]]</span>
 
<br /> <span style="font-size: 16px">Return to [[Creation or maintenance of test data]]</span>
<br /> <span style="font-size: 16px">Return to [[Maintenance expectations not met]]</span></div>
+
<span style="font-size: 16px">Return to [[Maintenance expectations not met]]</span></div>

Revision as of 14:34, 30 June 2018

Why is it difficult to reuse data?


Please select the item that describes best your current situation:

For the following items the issue of choice is TEST DATA LOSS:

  1. It's faster (and easier) to create new data than to try to reuse it
  2. Nobody knows what is already available


For the following items look up the issue INCONSISTENT DATA:

  1. You can only use the data once, then it gets corrupted
  2. Data is only valid for one release
  3. Data has to be updated from release to release


Return to Creation or maintenance of test data

Return to Maintenance expectations not met