Test Strategy & Test Plan

9:25 AM

Test Strategy & Test Plan

 Index

·         Test Plan
·         Test Strategy
·         Testing Environment
o  IT Environment
o  Equipment Environment
o  Data Analysis
o  Backup Database
o  Restore Database
·         Procedures
o  Problem Identification
o   Defect Rectification
o  Re-testing
o  Sign-off testing activities

·         Sign-off Testing

Test Strategy

Project Name

Overview

Testing stage Instructions:
Identify the type of testing to be undertaken.
Example:
User Acceptance Testing

Scheduled for Example:
01.04.06 to 15.04.06
Location Example:
Testing will be carried out in the Test Center on Level X
Participants Instructions:
Identify who will be involved in the testing. If resources have not been nominated, outline the skills required.
Example:
  1. QA Manager - J. Smith
  2. QA Lead
  3. QA (Quality Analyst)
  4. Testers - To be nominated.
The skills required are:
  1. QA Manager
    1. Discussion of Client,
    2. Release Management from Developer to Client,
    3. Prepare the Testing & Reviews Plan,
    4. Monitoring the major problem of Application, QA and Testing Team
  2. QA Lead
    1. Prepare the Testing & Review Plan,
    2. Manage the Build Releases & Rejection,
    3. Schedule, Assign & Priorities task to Tester & QA Team,
    4. Monitoring the Testing, Defects and Testing Process,
    5. Provide the guidance to QA & Tester Team
    6. Sign off the Testing & QA
  1. QA (Quality Analyst) 
    1. Writing & Reviews the Use Cases,
    2. Review the Test Cases, Checklist and Defects Documents,
  1. Testers
    1. Test Case Writing,
    2. Execution Test Cases,
    3. Find & Log the Defects,
    4. Retesting the Defects,
    5. Sign off the Testing
    6. Broad understanding of all the processes
    7. Should be familiar with manual processes
    8. Preferably spent time dealing with client

Testing Environment

 IT Environment

Instructions:
Outline the details of the environment to be used for testing.
Example:
Three test areas will be set up for testing.
1.      The first is to be used by the developers to carry out Unit Testing
2.      The second is to be used by the tester to carry out Integration and System Testing
3.      The third is to be used by the users to carry out User Acceptance Testing
of the data input and transaction processing. To access the first area, select “Environment 500” on the security screen. The second area will be used to test reports. This will be accessed as "Environment 501".
The following conditions apply to the environment:
  • Security access will need to be arranged through the System Administrator.
  • Users should have the ability to run month end processing

Hardware Environment

Instructions:
Identify the equipment required for testing.
Example:
We will require:
  • Total no of computers
  • Identify the Operating System
  • All with access to the LAN
  • A black and white laser printer
  • A colour printer

Data Analysis

Instructions

Identify the data to be used for testing.
Example:
"Environment 500" will contain:
• 1000 customers selected at random from out production database (every 2000th customer alphabetically).
• Transaction date ranges between 1990 and 2010 can be used.
• The database has no records for products x and y

Backup Database

Instructions
Identify how often data backups should be undertaken and who has responsibility for backups. Also cover how long backups should be retained.
Example:
Backups should occur:
• Nightly
• During the day at the request of the Test Manager
Responsibility for backups is listed below:
• Test Manager responsible for requesting backups at unscheduled times
• Test Manager responsible for delaying or canceling nightly backups
• Operations responsible for completing backups
Nightly backups should be a full backup. Unscheduled backups should be incremental backups.

Restore Database

Instructions:
Identify how and when a restore should take place.
Example:
The Test Manager will advise Operations if and when a restore is required to either do a complete refresh of the data or restore to a previous backup.

Procedures

 Process Identification

Use Cases Release

Analysis the Uses Cases
Attend the meetings by finding problem in use cases
Update the Uses Cases

Problem (Defect) Identification

Instructions:
Identify the procedure to be used when a tester finds a suspected defect. There should be a nominated resource to receive all defects. In some cases there may be more than one resource e.g. one person for applications problems and one for operational problems.
Example:
Step Action
1. Identify suspected problem
2. Refer to Test Lead/Manager
3. Does the Test Lead/Manager validate the defect
  • If yes, go to Step 4
  • If no, quit
4. Fill out a "Defect Logging Form" in Defect Tracker like Bugzilla, PVCS etc
5. Enter in the "Defect Log"
6. Forward to nominated resource for rectification

Defect Rectification

Instructions:
Identify how the defect will be managed once received. This procedure would normally be under the control of the person or people rectifying the defect.
Example:
Step Action
1. Receive a "Defect Logging Form"
2. Schedule the rectification based on the priority
3. Allocate all defects for investigation and rectification
4. If defect can be reproduced/validated
• Rectify and test the defect
• Go to Step 6
5. If defect cannot be reproduced/validated
• Discuss with Test Lead/Manager
• Go to Step 6
6. Return to Test Manager.
7. Update "Defect Log" under Defect Tracker

Re-testing

Instructions:
Identify the procedure for re-testing rectified defects.
Example:

Step Action

1. Receive rectified defect (Defect Fixed)
2. Discuss possible implications of rectification with the person who carried out the rectification
3. Determine the level of re-testing required
4. Draw up a test plan
Or
Identify what part of the original test plan will need to be repeated
5. Carry out testing
6. If testing is successful
• Update the "Defect Log" by signing off the fix
• Quit
7. If testing is unsuccessful
• Update the "Defect Logging Form"
• Return to the nominated person
• Update the "Defect Log" to show it is once again awaiting rectification

Sign-off testing activities

Instructions:
Identify the procedure that will be used to sign-off each activity in the testing. This includes both the testing outlined in the "Test Plan" and testing of defects that have been rectified.
Example:
Step Action
1. Carry out each testing activity in the "Test Plan" using the "Test Scripts".
2. If testing successful, go to Step 4
3. If unsuccessful, see procedure for "Problem Identification".
4. Sign and date the "Test Script"

Sign-off Testing

Instructions:
Identify how the total testing will be signed off. This includes all activities in the "Test Plan" and any rectification of defects.
Example:
Testing will be considered successful when the following conditions are met:
• All testing identified in the "Test Plan" has been completed
• No defects classified as severity "Critical" exist
• No defects classified as priority "High" exist
• Less than 3 defects classified as priority "Medium" exist
• Less than 6 defects classified as priority "Low" exist
• Outstanding defects classified, as "Medium" will be returned from rectification within 3 working days


0 comments

Post a Comment

Subscribe to: Post Comments (Atom)