Thursday, August 15, 2013

Test Case Design

User Interface based test case design:
 In general test engineers are selecting test cases depending on global user interface rules and prototype to conduct user interface testing.

  1. Verify screen elements contrast(i.e., distinguishable or not)
  2. Verify functional grouping of user interface elements(Ex: Date, Month, Year)
  3. Verify boarders of functionally grouped elements
  4. Verify alignment of the objects in the screen.
  5. Verify the font uniformity through out the screen.
  6. Verify the size uniformity through out the screen.
  7. Verify the spacing uniformity through out the screen.
  8. Verify the first letter of the label capitalized.
  9. Verify the instructions before the elements to which they apply.
  10. Verify the redundancy avoidance.
  11. Verify the full forms of the abbreviations(Ex: DOB (DD/MM/YYYY)
  12. Verify grouping of the buttons when that buttons are providing alternate functionality (OK, Cancel)
  13. Verify keyboard access of every control on the screen.
  14. Verify default object in every screen.
  15. Verify short cut menus without duplicates.
  16. Verify meaningful HELP messages.
  17. Verify uniform background color.

Business logic based test case design:
After preparation of usability test case writing, we test engineers concentrate on business logic based test case writing.
  1. Collect all required functional specifications.
  2. Select one functional specification from the list.
  3. Identify 
    • Entry point
    • Input required
    • Flow
    • Output or Outcome
    • Exit point
    • Alternative flows and exceptions.
  4. Prepare test scenarios
  5. Review those scenarios for completeness and correctness
  6. Prepare test cases for the reviewed scenarios.
  7. The above steps should be repeated until completion of all functional specifications.

Input domain based test case design:
After completion of user interface based and business logic based test case design, test engineers prepares input domain based test cases.
  1. Collect data models in design documents.
  2. Read data models to understand size, type and constraints on every input.
  3. Prepare Data matrix with above collected data. 
                                                  Format for data matrix




No comments:

Post a Comment