Some input data is fixed and available at the start of the test. Some is consumable, and forms the test input. Data can be loaded into the system manually, or by tools. The presentation discusses the advantages and pitfalls of various methods and suggests partitioning strategies to allow reliability and flexibility in the same dataset. The frequency and timing of data loading is also discussed.
Data maintenance is a substantial task, often comparable in size with test script maintenance.
The presentation discusses common problems and possible solutions. A key solution is that good data content can help reduce the workload of data maintenance. Good data can allow testing to carry on in areas not covered by the initial scripts and requirements. Naming conventions can help data to be accurate, and can make test results easier to interpret. A good test data structure promotes a common understanding and helps avoid mistakes.