Test Cases

Once testing begins the developers must create the test data, enter it into the system and write the test plan.

  1. The VENDOR must ensure that the test plan involving test cases is shared with the client at regular interval for review.
  2. The VENDOR  team (developers) and the CLIENT must mutually agree and define a scripting standard for creating test cases.
  3. The scripting standard used by the VENDOR must define the degree of detail required in test steps (e.g. weather a click by click level of instruction required OR just the basic action items).
  4. The VENDOR must break larger  tests to smaller ones.
  5. The VENDOR must ensure that the test data should be of good quality and well structured.
  6. The VENDOR must ensure that the test cases is in a written format, consistent in language, have a name, summary, description and steps, expected results and set up/clean up information.
  7. The VENDOR must create a checklist of items to test functionality and each functionality must have a test case.
  8. The checklist used by the VENDOR must be drawn to test new category of features (in case of system enhancement/modification), or for testing features requiring in-depth validation of huge quantity of data.
  9. The VENDOR must analyze the quality based on comparing the estimated and actual number of test cases (If actual>estimate would means estimate configuration incorrect and vice versa; thus assessing quality, productivity together).