A sample text widget

Etiam pulvinar consectetur dolor sed malesuada. Ut convallis euismod dolor nec pretium. Nunc ut tristique massa.

Nam sodales mi vitae dolor ullamcorper et vulputate enim accumsan. Morbi orci magna, tincidunt vitae molestie nec, molestie at mi. Nulla nulla lorem, suscipit in posuere in, interdum non magna.

How do you create and define test strategy? What are requirements in test Strategy?

It is a proven fact that one would go nowhere without a defined strategy and so the same holds for the software testing. A test strategy is required for a successful completion of testing process. In this article we shall outline what a test strategy is and its requirements.
“A test strategy can be thought of as an outline that gives description of the approach that is used in the testing process of SDLC or software development life cycle.”

The purpose of creation of a test strategy is for informing the following people regarding the issues that are encountered while the testing process is on:
1. Project managers
2. Testers and
3. Developers
And the issues consist of the following:
1. Testing objectives
2. Methods of testing new functions
3. Resources required for the software project
4. Testing environment
5. Total time
6. Methods of testing new functions

What is described by test strategy?

– It is described by the test strategy that:
1. How the mitigation of the product risks of the stake holders will take place at the test level?
2. Tests of what all types have to be performed?
3. Which entry and exit criteria are applicable?

Creating Test Strategies

– The creation of the test strategies is based up on the development design documents.
– The documents that are primarily used are of the system design.
– But in some of the rare cases, the conceptual design documents might be used.
– The functionality of the software that are to be included in the upcoming versions of the software system or application are described by the design documents.
– A strategy needs to be created corresponding to every stage of the development design so as to do the testing of the new feature set.
– Also, the test level which is to be performed is defined by the test strategy.
– There are 3 primary levels of testing namely:
1. Unit testing
2. Integration testing and
3. System testing

For the first level of testing, usually the developers are held responsible and for the other two, the test teams or individual testers take the responsibility.
– For every test strategy it is important that the roles and responsibilities of the following are defined:
1. Test leader
2. Individual testers
3. Project manager etc.

– There is no need to associate the names in the test strategy, however, the role has to be listed with clarity.
– After a testing strategy has been written it is passed on to the developers for review and is then further passed to test leads.
– This is to make sure that the coverage provided is 100 percent and void of any kind of overlapping.
– Before the team can step up on the test strategy it needs to be approved by the development managers and testing managers.
– Another important aspect of a test strategy is the environment requirements.
– This includes describing what operating system is being employed for the testing.
– Also, the security updates and OS patch levels are indicated here.
– Any of the two methods can be used for test case execution:
1. Manual and
2. Automated

– Nowadays, usually a mix of two is used.
– Mitigation part is to include all the risks that will affect the testing process.
– In order to anticipate the occurrence of a risk in future it should be well documented.
– In order to avoid mitigation of the damage of the risk some proactive actions need to be taken.
– A test strategy alone would not help rather it should be accompanied by a test schedule so that the time taken for the completion of testing could be estimated.
– In first step, all the test cases need to be executed one time for minimum.
– Next step, involves fixing the defects if any are found.
– Next, the failed tests need to be executed once again for confirmation.
– This phase of regression testing need to be carried on till no error is found.

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>