Software Test, QA & Support in the 2.0 World: The Collage of Devankur Thakur

# re: Test Case Checklist

its good one 3/14/2006 3:04 AM | rohan

# re: Test Case Checklist

Thankyou for the invaluable life lesson learnt from this article, in future I shall nail my penis to an Iron fence on a warm summers day instead.

Once again, thankyou. 10/14/2008 10:43 PM | tomvale13

# re: Test Case Checklist

Quality Attributes
- Accurate - tests what the description says it will test.
- Economical - has only the steps needed for its purpose
- Repeatable, self standing - same results no matter who tests it.
- Appropriate - for both immediate and future testers
- Traceable - to a requirement
- Self cleaning - returns the test environment to clean state

Structure and testability
- Has a name and number
- Has a stated purpose that includes what requirement is being tested
- Has a description of the method of testing
- Specifies setup information - environment, data, prerequisite tests, security access
- Has actions and expected results
- States if any proofs, such as reports or screen grabs, need to be saved
- Leaves the testing environment clean
- Uses active case language
- Setup offers alternative to prerequisite tests, if possible
- Is in correct business scenario order with other tests


In general

1) format of test case is appropriate
2) Test case should map to requirement so that no requirement got missed.
3) It should be easy to understand and in plane english language.
4) Test case include all pre requisite and test data, env. details.
5) No test condition should be duplicate.
6) Tester / Dev / expected date of completetion / author name date should be included.
7) Project / Module / name etc. should be there
3/19/2009 5:43 PM | Ravi Kochar

# re: Test Case Checklist

Thanks Ravi Kochar.. Its a great help 4/29/2009 9:07 PM | Ashutosh Kalra

# re: Test Case Checklist

- Is the test objective clear, unique, complete and unambiguous?
- Is every step numbered?
- Are Actions and Expected Results indicated for every single step?
- Are Preconditions indicated if required?
- Is the information clear and explicit so that it facilitates the test execution process?
- Are the instructions presented in order and step to step?
- Is easy understand the overall activities to be performed?
- Are the steps complete in the details for execute the Testing?
- Does the areas are focused on the functionalities to be tested?
- Is the test data correct if indicated?
- Is the record of changes updated?
- Is easy the redaction for understand without redundant writing?
- Is correct the spelling of the document? 1/10/2011 9:47 AM | Deya Araujo

# re: Test Case Checklist

Check list for writing test cases 9/22/2011 12:21 AM | yogitha