RSS

Daily Archives: June 1, 2012

Test Strategy Template


These are the most common sections:

1.Objectives
State the objectives of this document at a high-level.

2.Scope
State the scope of the testing strategy, what will the testing concentrate around, at high-level; leave details for the Testing Scope.

3.Test Deliverables
State the testing activities and what documents result from these activities; for example a testing activity is Test Planning and the document resulting is the Master Test Plan or Test Plan.

4.Testing Schedule
Give the timelines around which the project is planned and where testing fits in this schedule.
I find that a diagram has a high-impact on the user (a Georgia rule of thumb is that I use color and diagrams to break the boredom of the text).
Describe the diagram in words.

5.Test Scope
The Project Charter or Master Test Plan usually state all the items in scope, just copy and paste from these documents. Add anything that’s missing or has changed from the last review.
Then state any items that are Out of Scope.

6.Risk Analysis
State all the risk that you envision, the higher the risk – the higher the test priority.
When you start testing you will want to start with the high-priority items, then test medium-priority and if time permits test low-priority functionality.Risk Analysis is very important from this point of view because it drives the whole test strategy. When giving the risk state how to you plan to mitigate (to alleviate, to make less severe) and what is the contingency plan (back-up plan in case this happens).Additionally you may want to say what is the impact of each risk.

kevalshah.in

Read the rest of this entry »

Advertisements
 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

System Test Strategy Template



Provided by Rex Black Consulting Services

  1. Product, Revision and Overview

Describe the product and revision designator.

Describe briefly how the product works. Reference other material as appropriate.

  1. Product History

Include a short history of previous revisions of this product. (3-4 sentences). Include defect history.

  1. Features to be tested

List all features to be tested. Organize the list in the way that makes most sense- user features, or by level:

Application
Demo software
Client substrate
Server
Network (this may be more layers)
  1. Features not to be tested

Describe any features not to be tested

  1. Configurations to be tested and excluded

I recommend a table showing which hardware configurations will be tested with which software.

  1. Environmental requirements

Enumerate hardware, firmware, software, networks, etc. required to carry out the testing.

  1. System test methodology.

Brief description of work items to be performed from the beginning to the end of the product development.

  1. Initial Test requirements

Test strategy (this document), written by test personnel, reviewed by product team, agreed to by project manager.

  1. System test entry and exit criteria
kevalshah.in

Read the rest of this entry »

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

test case format -sample


unique-test-case-id: Test Case Title

Purpose:

Short sentence or two about the aspect of the system is being tested. If this gets too long, break the test case up or put more information into the feature descriptions.

Prereq:

Assumptions that must be met before the test case can be run. E.g., “logged in”, “guest login allowed”, “user testuser exists”.

Test Data:

List of variables and their possible values used in the test case. You can list specific values or describe value ranges. The test case should be performed once for each combinationof values. These values are written in set notation, one per line. E.g.:loginID = {Valid loginID, invalid loginID, valid email, invalid email, empty}password = {valid, invalid, empty}

Steps:

Steps to carry out the test. See step formating rules below.

  1. visit LoginPage
  2. enter userID
  3. enter password
  4. click login
  5. see the terms of use page
  6. click agree radio button at page bottom
  7. click submit button
  8. see PersonalPage
  9. verify that welcome message is correct username

Notes and Questions:

  • NOTE
  • QUESTION
kevalshah.in

Read the rest of this entry »

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

 
%d bloggers like this: