As a tester, it’s our responsibility to design and maintain the test cases with high standard. For that, we need to follow certain standards/characteristics in order to maintain the test cases with high quality and reliability. Every organization/individuals follow their own set of instructions in the testing design process.
The important characteristics are,
The test case description and expected result need to be a very simple language where other can easily understandable.
Do not keep lengthy test cases, break into small ones which will make our job easy for doing impact analysis and for regression test suite identification and execution.
Below would give you an idea of breaking of test case,
Test case1 – Before job runs verification steps
Test case2 – Data setup
Test case3 – Running job and checking status of job
Test case4 – Data count and data comparison check
Test case5 to n-1 – Separate test case for every transformation
Test case6 – Negative case
Test case7 – Performance check
Must have SQL Query:
I have come across situation that some of the test steps do not have SQL query itself, because of this tester need to form the SQL query during test execution time, it will end up in below,
Manual errors might occur due to tight schedule of test execution
Valid SQL Query:
Always execute the SQL query before uploading into test case repository since there are chances that the query could throw errors. Also, use right built-in function and join type and condition appropriately.
Up to date:
There are chances happen like on job name, log filename, parameter file names, paths could be changed. The ETL test case needs to be updated based on all modifications.