If you start thinking about testing during the coding process, you're too late.
You should begin to plan your testing during the analysis phase. Step one is to
formulate a Testing Strategy.
The test strategy is a formal description of how a software product will be tested.
A test strategy is developed for all levels of testing, as required. Our test team
analyzes the requirements, formulates the test strategy and reviews the plan with
the project team. The test plan may include test cases, conditions, test environment,
a list of related tasks, pass/fail criteria and risk assessment.
The purpose of the Testing Strategy is to define the overall context for the entire
testing process. The process is different depending on the specific characteristics
of your solution.
We at Pulse Solutions provide complete coverage for your tools and strategies and
where required we can pass on this knowledge within the project or within the whole
company. Pulse Solutions' test strategy provides companies the ability to implement
a company wide strategy quickly and easily.
We recognize that there are no fixed test strategies. Each test strategy and client
requires a unique solution.
Basic parts of a test strategy document:
Project Overview: Gives the
overall project overview.
Business Risks: These are
high-level risks of the project that will affect the overall testing strategy.
The risks are classified as high, medium, and low, depending on the nature and impact
of the problem.
Testing Milestones: This section
gives the preliminary overview of the testing timelines.
Testing Approach: This describes
the testing process at a high level, including how you will conduct unit testing,
integration testing, system testing, and acceptance testing. For system testing,
define the major testing events, such as stress testing, security testing, disaster
recovery testing, usability testing, and response time testing.
Testing Environment: Analysis and documentation of the solution technology and infrastructure required for testing e.g. Hardware and Software needs.
Depending on your project, there may be other high-level sections to include, such
as testing objectives, testing assumptions, testing organization, and testing tools,
along with effort and cost estimates.