TestingGeek

Learn, Share and Keep Learning

Home Testing Templates

Templates

In this section TestingGeek will provide guidelines on preparing certain documents and verifying others. These guidelines are provided in the form of templates and checklists. You can consider them as a starting point and can always customize them to meet your project needs.

For ease of understanding, this section is divided into two parts, templates and checklists.

Requirement Verification

Checklist Guidelines
It is a well established fact that early involvement of testers during the software development life cycle brings immense value to the project. Participation of the testers during the requirement phase helps in identifying and correcting defects in the requirements.

As a tester if you are involved in the requirement phase you need to know , what attributes you should be looking for in the requirements? How can you ensure quality of the requirements? Following checklist gives you information about the attributes which should be tested for every requirement. These are just a subset of attributes that as a tester you will be interested in.

Last Updated ( Wednesday, 28 January 2009 15:18 ) Read more...
 

Defect Report Template

Testing Templates
Defect reports are probably primary work product for most of the software testers. Good bug report, which is informative and understandable earns you a good reputation. Weak report generate extra work for everyone. Most of the time, a weak bug report is returned with comments saying not clear, need more information etc. That makes you work again on the same defect and thus reduces efficiency of testers and developers both. Defect reports are not only used by programmers, but also by managers, executives, documentation team and support executives for various reasons.

Read more...
 

Test Plan

Testing Templates

Test plan is probably one of the most significant document for software testing projects. Test plan may contain information related to scope, environment, schedule, risk, resources, execution, reporting, automation, completion criteria etc. Test plan is usually created by Test Manager, Test Lead or senior testers in the team. Before start preparing Test Plan, information should be captured from various stakeholders of the project. Information captured from stake holder is reflected in the Test Plan.

Read more...
 
Page 2 of 2

Stay in touch

Enter your email address:

Delivered by FeedBurner

Your Opinion Matters

Defect found by testers is
 

What's Popular

Follow Me - Twitter

Follow me on Twitter @ TestingGeek

Services.

Do you need reliable and efficient testing services covering all aspects of software testing? Contact Atlantis Software for all your software testing needs.

Check Websites

If you are looking for easy and cost effective way of checking and monitoring your web application and websites - try iCheckWebsite