testcasetype

Retrun to HomePage

Overview

Its a test case to verify if certain guidelines etc are implemented correctly. More useful for tester community.

Schema

* Title
* Applies to
* Objectives
* Overview
* Summary of Steps
* <<Step N>>
* Repro Example
* Tools Support
* Additional Resources
* Related Items

Test Cases

Title
* Is title in the form of "How to Test For xxxx"?
* If the test is to uncover a potential issue, does title contain the issue you are trying to uncover (eg. SQL Injection, Buffer Overflow)?
* If the test is to verify correct implementation or design does the title contain what you are trying to verify (Input is properly validated for length, range, format, type)?

Applies to
* Does the list contain specific technology and version (eg. ASP.NET 2.0)?

Objectives
* Are the most important learnings from the document extracted into the objectives?
* Is each objective expressed as a specific task?
* Is the objectives list short enough that it can be easily scanned and understood?

Overview
* Does the overview provide enough background information to understand why it is necessary to take the steps?
* Does the overview provide enough information that the module can stand alone?

Summary of Steps
* Is there a numbered list the explains each step in the document?
* Do the steps match to the document sections exactly?

<<Step N>>
* Does each step explain what to do, why it is important and then how to take action?
* If there is a decision point is it called out with an explicit ‘if…’ condition?
* Is the document capable of standing alone without requiring the user to search elsewhere to complete the testing procedure?
* Where appropriate, are there code or configuration file examples?

Repro Example
* Is there a Flawed Code section that contains an example of what the flaw looks like in application code or configuration files?
* Is there a Test Example section that shows what a tester would have to do to expose the flaw?
* Does the Test Example contain real user input or steps that would result in a bug in the real world?

Tools Support
* Are all the relevant tools useful for test case listed?

Additional Resources
* Are the links from trusted sites?
* Are the links correct in context of the test case?

Related Items
* Are the correct items linked in context of the test case?

Additional Tests to Consider When Writing a Test Case
* Is title in the form of "How to Test For xxxx"?
* If the test is to uncover a potential issue, does title contain the issue you are trying to uncover (eg. SQL Injection, Buffer Overflow)?
* If the test is to verify correct implementation or design does the title contain what you are trying to verify (Input is properly validated for length, range, format, type)?
* If the item is a MUST, meaning it is prevelant and high impact, is Priority = p1?
* If the item is a SHOULD, meaning it has less impact or is only applicable in narrower circumstances, is Priority = p2?
* If the item is a COULD, meaning it is nice to know about but isn't highly prevelant or impactful, is Priority = p3?
* If this item will have cascading impact on application design, is Type = Design?
* If this item should be followed just before deployment, is concerned with configuration details or runtime behavior, is Type = Deployment?
* If this item is still in progress or not fully reviewed, is Status = Beta?

Return to HomePage

Overview

Schema

Test Cases

Example

Template

Links