The
concept of software testing seems like an amalgam of similar terms, all mixed
up in to each other. We all get confused sometimes between the different but
similar sounding terms.
For greater understanding of the software testing,
one needs to know exactly what all the inclusive terms mean and how and where
they are used or implemented. This piece of writing is dedicated to the cause
of removal of such confusions. In this article we are going to clear three
major concepts of software testing namely test plan, test strategy and test
scenarios.
1. Test Plan
- It does the same as a normal plan
would do i.e., detail out a systematic approach to the accomplishment of a
certain task.
- For
the test plan the task is the successful completion of a particular software
testing.
- A test plan gives a detailed approach of all the processes or
activities to be undertaken during the testing.
- A test plan marks the work flow
of the software testing mechanism.
- A test plan states the strategy to be
followed to make the software testing successful.
- It provides a means to check whether or not the software system or
application meets all the requirements and specifications as mentioned by the
client or the customer in the documentation.
- The test plan is usually created
by the testers.
- A typical test plan includes the following fields:
(a) Compliance test or design verification: performed on the product samples
while the actual product is in development stage.
(b) Production test or manufacturing: performed during the assemblage
process of the product for assuring quality and performance.
(c) Commissioning test or acceptance: performed while the product is being
installed.
(d) Repair test or servicing: performed during the product’s service life.
(e) Regression test: performed on an existing version of the product to
ensure the working of the functionalities.
- The
level of the design of the test plan depends on the complexity level of the
software system or application.
- For more complex systems high level test plans
are created.
- Apart from the above mentioned tests, a typical test plan must
cover about the test methodologies, test coverage and test responsibilities. - It
also states what all requirements are to be verified in the testing.
2. Test Strategy
- Test strategy
forms an essential part of the test plan.
- To put it simply we can say that the
test strategy is nothing but a superficial sketch or outline of the actual test
plan of the software development cycle.
- A test strategy is developed just to
inform the project developers about the approach that is to be followed during
the testing.
- The key components of a typical test strategy are objectives of
the testing, test methods, test duration, resource requirements and test
environment.
- Test strategies give the description of the risk mitigation, tests
to be carried out and not to forget the entry and exit criteria for the tests.
- For each level of software testing, an individual test strategy is created.
3. Test Scenario
- Test scenarios
form an essential component of the scenario testing.
- These test scenarios
provide a hypothetical measure to help the tester out of some complex problem
encountered during the testing.
- The main characteristics of a typical scenario
are its complexity, credibility, motivational story with a reasonable outcome.
- The scenarios are usually lengthy as compared to the length of the test cases
probably because of more number of steps are present in a test scenario. 2 or
more scenarios together make up a scenario file.
