Search
Sign In
Home
Recent
Media
Videos
Podcasts
Screencasts
Learn
Shows
This Week On Channel 9
Going Deep
The Knowledge Chamber
See All Shows...
Forums
Coffeehouse
Tech Off
Feedback
Sandbox
Key Topics
Visual Studio
Continuum
Identity
Interoperability
Azure
Windows
Wiki
Search
Subscribe
guidelinetestcases
Cancel
Edit
[WikiEntry.PreviewButtonText]
Save
Return to
HomePage
Guideline Test Cases
Title
*
Does the title clearly state the action to take?
*
Does the title start with an action word (eg. Do something, Avoid something)?
Applies To
*
Do you list technology and version? (e.g. ASP.NET 2.0)
What to Do
*
Do you state the action to take?
*
Do you avoid stating more than the action to take?
Why
*
Do you provide enough information for the user to make a decision?
*
Do you state the negative consequences of not following this guideline?
When
*
Do you state when the guideline is applicable?
*
Do you state when not to use this guideline?
How
*
Do you state enough information to take action?
*
Do you provide explicit steps that are repeatable?
Problem Example
*
Do you show a real world example of the problem from experience?
*
If there are variations of the problem, do you show the most common?
*
If this is an implementation guideline, do you show code?
Solution Example
*
Does the example show the resulting solution if the problem example is fixed?
*
If this is a design guideline is the example illustrated with images and text?
*
If this is an implementation guideline is the example in code?
Additional Resources
*
Are the links from trusted sites?
*
Are the links correct in context of the guideline?
Related Items
*
Are the correct items linked in the context of the guideline?
Additional Tests to Consider When Writing a Guideline
*
Does the title clearly state the action to take?
*
Does the title start with an action word (eg. Do something, Avoid something)?
*
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
Cancel
Edit
[WikiEntry.PreviewButtonText]
Save
Delete
Edit
Comment on Post
Delete
Edit
Reply
In reply to {0}
Download:
[Pending]
Delete
Edit
Reply
In reply to {0}
Download:
[Pending]
Delete
Edit
Reply
In reply to {0}
Download:
[Pending]
Delete
Edit
Reply
In reply to {0}
Download:
[Pending]
Delete
Edit
Reply
In reply to {0}
Download:
[Pending]
Delete
Edit
Reply
In reply to {0}
Download:
[Pending]
Delete
Edit
Reply
In reply to {0}
Download:
[Pending]
Delete
Edit
Reply
In reply to {0}
Download:
[Pending]
Delete
Edit
Reply
In reply to {0}
Download:
[Pending]
Delete
Edit
Comment on Post
Be the first to comment!
Reply
Reply to root
In reply to {0}
Start related discussion
Forum:
Site Feedback
Tech Off
The 9 Guy Around The World
The Coffeehouse
Subject:
Tags
*Loading available tags