|
Zephyr is contextual based
on the organization of projects and the releases that it
contains. A strict process can be applied and all test cases, documents, schedules,
execution, reports, metrics and dashboards are kept
contextual to a particular release and accessed
appropriately.
How Zephyr
integrates with this process
For departments employing
the V-Model, Zephyr is set up to have multiple
releases within each project. For each release, during
the Requirements Analysis Stage requirements documents are
created by the Business and these are linked or uploaded
within the Documents application. During the System
Design Stage, the Test Case
Repository is used to plan and track
major/minor requirements as well as address all aspects
of a Test Plan including the various phases of testing
(Acceptance, Functionality, Regression, Integration
etc.). Based on the requirements and the design
documentation/POCs available during the Architecture
Design and Module Design Stages,
detailed test cases are created by various testers
assigned to this release and a review process set up.
Once the test cases have
been authored and reviewed and the software is ready to
exit the Development Stage and into Unit Testing, a detailed Test Execution
schedule is created and appropriate assignments to
different testers done. Now, test case execution begins
in earnest and the test-file-fix-retest loop is put in
place with the Testcase Execution and Defect Tracking
applications. Various test cycles are created within
Zephyr to align with Integration Testing, System Testing
and final Acceptance Testing Stages.
Zephyr tracks everything
automatically and produces live metrics on all key
Stages of the testing cycle, constantly measuring
productivity and quality of the software under test by
reporting on test case creation,
coverage, test execution progress and defects.
Major
Advantages of Zephyr in the V-Model:
1. All testing organized
according to the process being followed and aligned with
the Stages
2. Ability to maintain rigor in the testing process
3. Ability to handle multiple testing cycles for System,
Integration and final Acceptance
4. Track productivity and quality at a granular level
|
