Blog

Self review checklist: Test Casing (The Pragmatic Testing)

On October 17, 2011, in Syndicated, by Association for Software Testing
0

{ 05:09, 2008-Sep-13 } { Posted in Software Testing} { 0 comments} { 2271 trackbacks} { Link}

I made it mandatory for most of the projects to self-review the test cases one is writing (most of, because processes must not be cast in stone; as a tester one is expected to be pragmatic & context driven). Even though peer review was in process, we embraced this practice to make sure we do not get review defects. It was a good decision and we could ward off major defects due to this. I would like to thank Rex Black as he is the one who always encouraged use of checklists. 

The checklist is pasted below. It is not a copyright or IP material. You may use it or edit it the way you want. After all, it was created in MS Excel.

#
Self Review Checklist
1
Spell Check was run
3
Test Status updated
4
Document Control section properly filled
5
Requirement ID is filled against each Test Case
6
Test Case ID column is properly numbered
7
Page Setup has been checked using Zoom option:
– Page Margins are set to adjust the text
– Filled sections are bordered in ‘Black’ color
– Row & Column spacing is justified
8
Fonts Consistent
9
Metrics sheet is reflecting the actual number, if not update the sheet consulting TL
10
Test cases which are changed / modified in particular version are changed to ‘Light Blue’ font color
11
Test cases with pending queries are highlighted with ‘Gold’ highlighter
12
Prerequisites are filled wherever applicable
13
Navigations are specified if present in the requirement document
14
Test Data is filled wherever applicable.

 

Comments are closed.


Looking for something?

Use the form below to search the site:


Still not finding what you're looking for? Drop a comment on a post or contact us so we can take care of it!