My question is ...
i need to prepare test data. what should be there/ready , Which info. is needed for writing test data. what are the things to consider for test data. when the test data is prepared. I am totally new. I have Bussiness specifications and asked to prepare test data.
Re: Test Data
this could be quite a big thing depending on the size of the task and the drivers behind it.
Some generic pointers first, then we can add more details once we have a better grasp of your situatuion...
1/ is the data required going to be used across multiple systems. If it is ensure the systems are all syncronished at where the data cut was taken.
2/ Ensure when the data cut was taken no systems were in a transactionla state.
3/ look to collect data arond field bounderies and systems boundries as this can assist in finding defects.
4/ Lean on the business to find data that is representative of what they are using - it can be useful to take a cut of live and then cleanse it (useful and a legal requirement in some countries).
5/ Use Scenarios and stories to build tests and build data life histories, transactional paths through the system, with check points for the testing.
6/ If load testing take a range of data types and be sure to keep it in a manner that can be randomised, so keep the interdependancies low, and use equivilance groups to increase coverage.
7/ consider using negative data, ie invalid or obviously wrong but valid, to see the effect of this on the system and its integrity.
Useful infomation to create test data - business knowledge (specs, use cases, stories, entity life history diagrams, data definitions), systems walk throughs and application knowledge can add value to.
Re: Test Data
Thank u very much Neil. This info. is very useful for me.