Information Technology Reference
In-Depth Information
Project Development Phases
Corresponding Te st Phases
Te st Case Writing
Phase
Requirement Phase
Automation Design
Phase
Design Phase
System & Regression
Te sts
Build Phase
Deployment Phase
Acceptance Te sts
Production Phase
Sanity Te sts
Figure ..2
Software development phases and corresponding test phases.
keyword-driven automation frameworks are discussed in detail in
Chapter 9.4
of this topic).
In the V-Model, the requirement phase is linked to the User Acceptance Test,
the design phase is linked to the System Test, and the build phase is linked to
the Unit and Integration Test. But this model does not describe exactly when test
design, test case writing, and test case execution should take place. It also fails
to integrate automation-related activities of automation framework creation, script
design, and script creation in the model.
So here is a modified model that removes these shortcomings of the V-Model
(see Figure 3.2).
Referring to the figure, you can see that there is a matching phase for soft-
ware testing to each software development phase. In fact, these phases are not cor-
responding but rather subsequent phases. So the requirement phase leads to the
test case writing phase in software testing. The software requirement specifications
document is the input for test case writing. The output of the design document
is the input for the test automation design phase. Here you create your keyword
framework, create automation scripts, and create your test data. After the build
phase, you can create the test environment and start executing your system, regres-
sion, performance, and other tests. Here there will be iterations as the development
team fixes reported defects and the test team verifies the fixes. Once these tests and
fixes iterations are over, the system is handed over to the deployment team. Once
deployment is done, the test team runs sanity tests and performance tests daily or at
