Test Strategy is not only document

The purpose of Test Strategy document is in high level definition for entire Test management process and all related activities primarily in concept approaching into test preparation and test execution phases of project. Cooperation all testing activities during the project should be based on main Test policy of organization.

Test management processes

Implementation of testing processes is distributed into levels between organization, project and dynamic testing processes. 

Organization Test Policy is methodology and document which govern and describe rules for continuous improvement for testing activities within company and describes those areas:

Testing definitions, Test process descriptions, Testing Evaluations rules, Quality level definitions and Process improvement rules.

Test Strategy (this document) is artefact describes rules and global test approach used by project to deliver quality assurance for defined scope of applications, modules or whole systems with respectation of definitions from Test Policy.

 

Test Management processes govern primarily those activities:

Test planning - define approach for test plan implementation into partial test levels

Test monitoring and control - define approach for measurement test metrics

Test completion - include definitions for test finalization, testing evaluation summary and closing test activities.

Dynamic Test processes govern primarily those activities:

Test analyses - define test cases and test script structure and rules for writing at all.

Test environment definition – define governance for procedures of testing environment managing, support activities required for nonproblem flow of test implementation

Test execution – describe way how will be given test level covered by tests with ensure monitoring of all defined and required metrics for this activity.

Reporting – define elements and artefacts to be gather for storing project status from testing point of view.

Test process

Common test process serve definitions for test analytics, testers and other participant on test activities about description how testing would works for project.

Test policy and Test strategy could define and describe basic concept of test approach and other High Level artefacts description. Level test plan encapsulate detailed information about Level test activities for unit, system, integration and user acceptance tests.

Planning and control process cover specification for all test types required for project.

Planning include those activities and tasks:

·       definition for scope, target and risk of test

·       test coverage definitions, entry and exit criteria validation

·       integration and coordination test activities into development model

·       schedule definitions

Controlling activities cover:

·       measurements and result analyses

·       monitoring and progress documentation

·       test coverage and evaluation for exit criteria met

·       corrective actions to try to achieve the best possible outcome for the project

 

 

Analysis and design are activities, where during which execution global information from project documentation are implemented into refined test scenarios and test scripts.

Within this activity are covered the following tasks:

·       Project documentation review

·       Test requirements definition

·       Testability of project requirements

·       Identification and definition of test scenarios

 

Implementation and execution are activities, where during their realization global information from project documentation are refined into test scenarios and test scripts.

Within this activity are covered the following tasks:

·       Project documentation review

·       Test requirements definition

·       Testability of project requirements

·       Identification and definition of test scenarios

 

Evaluation “Entry and Exit” criteria are activities which compare defined and current metrics on project.

Within these activities are covered the following tasks:

·       Control test analyses and test execution progress with planned status

·       Evaluation about testability

·       Test coverage, code coverage, defect metrics

 

Reporting and Closing are activities for confirmation or escalation statement about deliverables or to met defined range of scope like:

·       Validation for testing deliverables

·       Milestones evaluation and lessons learn preparation

·       Testing evaluation summary preparation and acceptation

·       Test bed finalization and artifacts freezing.

 

Escalation procedure

Escalation flow for problems solving and for cases related with unclear information or new created situations during all phases of projects and related to software testing. Purpose for escalation is to prevent or reduce material or immaterial damage. Escalation will take place for case, where parties are Escalation will follow the general project escalation procedure, with the following escalation flow:

• Test managers
• Project Manager
• Steering Committee
• Company representatives

Defect management

Defect management process of capturing, reviewing, assigning, fixing and deferring defects throughout the systems development process. The same basic process can be followed for all test stages and for all defect types.

The progression of a single defect from creation through resolution, including:

• Logging a defect,
• Reviewing and validating a defect,
• Assigning, deferring, or rejecting a defect,
• Fixing a defect,
• Testing a defect (through Test Execution),
• Closing a defect.

Defect monitoring includes ensuring that defects are resolved with appropriate documentation and reporting on status and metrics. The management and monitoring of the defect process, including:

• Ensuring that defects are resolved with appropriate documentation,
• Reporting on status and metrics.
Any deviations from accepted requirements and specification documentation identified during testing are considered as defects. During test execution as well any issues concerning malfunctioning of test environment infrastructure are reported as defects and assigned to the respective team. 

Defect Severity

Detected defects during the testing will be classified into either of the severity categories defined in table below.

Severity	Description
1 – Showstopper	Fault causes total loss or failure of business-critical functionality, unrecoverable data loss or corruption. Usage of the system/application is not possible. No acceptable work around. Example: it is not possible to log into the application or to create any order).
2 – Critical	Fault causes partial failure or severely impaired functionality of business-critical functionality. No acceptable work around. Example: it is not possible to create modification order/ open eConfigurator.
3 – Serious	Fault causes failure of non-critical aspects of the system, or there is an acceptable work around.
4 – Minor	Fault causes partial failure of non-critical aspects of the system. An acceptable work around exists or the failure can be tolerated.
5 – Cosmetic	Fault is accepted but it is not necessary to fix it.