...

Testing Framework

...

Tailoring Approach to Testing

Testing as a cognitive, critical and often creative process.

...

Avoid over-administrative approach; no one-size-fits-all. Schematic and formal application and implementation of the standards, or procedures templates “by the book”, this document included, endangers to petrify, bureaucratise, and over-proscribe validation and testing process and impede innovation. What matters is the quality. However, running production-level services may require formalized processes, traceability or even auditability of validation, and particularly of check procedures.

Generic Testing Process Diagram

General Testing and Validation Governance

This document provides GN and, more specifically, GN4.1 SA4 with a generalised technical specification for testing and validation. It can be seen as a a contribution to the general specification of GN approach to validation and testing, on the base of its the overall testing policy (for implementation and management of services -  any sources/refs?), and as an (tentative?) technical expression of the shared testing strategy.

...

Should be periodically reviewed and updated on the base the experience from the actual performed tests, organizational and environmental changes and evolution of overall policies and goals. It is (one of / input for) general GN-level testing related policy and strategy documents.

Evaluation Planning

Need to familiarize with the context in order to define the scope, organize development of the test plan, identify and estimate risks, establish approach towards risks, design test strategy, determine staffing profile and schedule, draft test plan, establish consensus/get approval for the plan, publish the plan.

Traceability is the key characteristic of both Evaluation and Test Enactment related artifacts. Repetability for tests related to core requirements and functionality.  No need to repeat and maintain repeatability of tests that were already done unless possible to fully automate or required for compliance or periodic audits.

Test Enactment

Test design including test specification and design requirements, test environment set-up, test execution and related reporting.

...

Possibly provide  suggestions or inputs for the update of the general Testing and Validation Process and Strategy.

Test Documentation

On the common industry practices and with the strong influence from IEEE 829, and its sequel/update ISO/IEC/IEEE 29119-3, which even provides even templates for both traditional (sequential and iterative) and agile approaches.

Organisational/

...

Strategic Level

Policy and Strategy, also mandating the overall approach on validation and testing on base of documents such as this one.

Evaluation Level Documentation

For a specific service, product or solution

• Test Plan
• Test Status Report
• Test Completion Report

Test Level Documentation

• Test Design Specification
• Test Case Specification
• Test Data Requirements
• Test Data Report
• Test Environment Requirements
• Test Environment Report
• Detailed test results (base for status and completion reports on the base of individual tests execution logs and anomalies/incidents reports)