Software Test, QA & Support in the 2.0 World: The Collage of Devankur Thakur
"It ain't braggin' if you can do it."-Dizzy Dean, 1930's baseball player
Home
Contact
Login
News
Article Categories
Client/Server
CheckLists
Test Design
SQA & Test Process
Life Cycle and Models
Testing Web Services
Templates
Test Approach
Localization
Testing Basics
Test Automation
Risk Analysis
Security
Archives
November, 2008 (1)
October, 2008 (1)
May, 2008 (2)
April, 2008 (1)
February, 2006 (1)
July, 2005 (2)
June, 2005 (1)
May, 2005 (2)
April, 2005 (2)
March, 2005 (2)
February, 2005 (3)
January, 2005 (3)
December, 2004 (2)
November, 2004 (7)
October, 2004 (6)
September, 2004 (12)
August, 2004 (18)
July, 2004 (3)
June, 2004 (5)
Post Categories
Personal Diary
Software Testing
Generic
Test Tools
Image Galleries
My World..!
Lighter Strokes..!
Tech Stuff..!
Blogs to Read..!
>Bret Pettichord's weblogs!
>Brian Marick's weblogs!
>Cem Kaner's weblogs!
>Elisabeth Hendrickson
>James Bach's weblogs!
>Johanna Rothman's "Managing Product Development" weblogs!
>Jonathan Kohl's blogs!
>Micheal Hunter's weblogs:"The Braidy Tester"!
My Other Blog..!
-A little collage of life-
Software Testing Related Links
>Brad Appleton's Software Testing Links!
>Model-Based Testing!
>QAForums!
>Software QA and Testing Resource Center!
>Software Testing Hotlist by Bret Pettichord!
>Xtreme-Testing!
Syndication:
RSS
ATOM
<< Key Considerations in Performance Testing
|
Home
|
Free OpenSource Test Management Tool >>
Test Case Checklist
Test Case Checklist by Dianne Runnels:
http://www.stickyminds.com/r.asp?F=DART_2157
posted @ Friday, December 10, 2004 11:42 AM
Feedback
#
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
Post A Comment
Title:
Name:
Email:
Website:
Comment:
Verification:
Enter the code shown above
Remember Me?