Test Strategy Document

7 Steps to Develop Good Test Strategy Document

Test Strategy is very important for QA team. It defines the main goals that need to be achieved and the main measures used to implement these goals into reality. Clearly articulated plan determines the scale of the project and helps team to take into account all the activities related to testing process. Unfortunately, many testers build such documents but don’t use it while test execution. Let’s try to consider the common steps of test strategy document:

Test Strategy Document

Step #1: Scope and overview

The next aspects should be covered on this stage:

  • determining persons who should approve, review and use this document,
  • defining phases of the project in accordance with timelines with specified in the test plan, and
  • other elements that can be included in this document at the discretion of its sides.

Step #2: Testing approach

This step should be developed most carefully to avoid further messy in case if something going wrong. And the main issues that should be considered are:

  • distribution of responsibilities among team,
  • determining test owners, when to start, testing approaches, tool if applicable, etc.

Step #3: Testing environment

The main questions that should be covered aimed at defining the next aspects regarding test data:

  • requirements – the clear instruction on how to create test data should be provided;
  • backup and restore strategy aimed at ensuring that you won’t loss any data due to code issues.

So, try to choose people who will take backup, to detect when it should be taken and when to restore data.

Step #4: Testing tools

Now you need to choose all the tools will be used while test execution. Take into account whether it is commercial or open source tool, the scale of its community, etc.

Step #5: Release control

To ensure successful test execution, make sure your release management plan had been created thoughtfully. Thus, set build management process to know forward where new build should made available, deployed, when to get new build, etc.

Step #6: Risk analysis

Try to foresee all the possible risks related to your project. Build a clear plan to avoid such risks and a contingency plan in case of realization of the risks.

Step #7: Review and approvals

The ready plan must be verified and confirmed by managers, team leads from system administration team, business team and development team. Also test strategy document can be updated with testing process latest changes.


About helenbeck


3 comments

  1. December 21, 2012 @ 4:43 pm Abhijit Dehadrai

    Hi,

    Thanks for sharing the high pointers towards creating Test Plan/Strategy.

    I would appreciate if could share more details on each pointers, rather would suggest to emphasis more “Test Approach” this is the critical & most important area of test planning where we need to lots of efforts.

    Thanks,
    Abhijit

  2. April 14, 2013 @ 3:40 pm Jones sabo abercrombie gear linking based in london bracelet

    I was looking at some of your articles on this internet site and I conceive this site is very informative! Keep on putting up.

  3. May 2, 2013 @ 11:13 pm Jones sabo

    I really like your writing style, good info , thank you for posting


Would you like to share your thoughts?

Software testing & QA blog by TestFort © 2017

×