Irrespective of the Software Development Life Cycle (SDLC) implemented e.g Waterfall or Agile, there will be organisational and project specific test processes underpinned by appropriate artefacts.

Example evidence could include but not constrained to:

• Test Policy
• Test Strategy
• Test Plans
• Risk identification process as applied to Solution testing
• Irrespective of the Software Development Life Cycle (SDLC) implemented e.g Waterfall or Agile. How is testing within development phases established, such as;
  
  • Unit
  • Module or Component
  • System or Functional
  • Integration (including APIs)
  • Performance and Load Testing
  • Scalability, Resilience and Recovery Testing
  • Security Testing
  • User Acceptance Testing
  • Usability Testing
  • Accessibility Testing
• How testing automation is incorporated into the software build and distribution process, such as continuous build integration
• Testing Qualifications within Supplier organisation
• Retrospective process improvement

All

TEST-2

There will be Test Management Processes covering test planning and design.

Example evidence could include:

• Test Automation (automated scope as opposed to manual testing automated)

• Test Regression and process for establishing coverage scope during a specific and subsequent Solution releases

• Covering both Functional and non-Functional Testing

• Techniques used e.g. Risk-based, static/dynamic testing, testing heuristics, exploratory testing, smoke testing

All

TEST-3

There will be Test Management Processes covering test execution and management.

Example evidence could include:

• Tooling used, explaining how results are captured

• Test Execution Management

• Repeatability

• Defect/Incident Management

• Test Environment Management

All

TEST-4

There will be Test Management Processes covering test completion and Reporting.

Example evidence could include:

• Comprehensive test results captured within test tooling

• Incident management on completion

• Quality Criteria for exiting testing

All

TEST-ENV-5

In addition to a functional test environment, the Supplier must ensure that a non-functional test environment is available to do Volumetrics and Performance testing and other non-functional testing for their Solution.

All

TEST-ENV-6

The Supplier shall support end-user organisations to aid training of their users on the Supplier Solution(s). This includes Solutions with Spine connectivity, including all Core Messaging and CIS services, enabled through integration with the SPINE Training environments.

All

TEST-ENV-7

The Supplier must ensure that their test environments support robust access controls (security features) both at Solution level and Infrastructure level so that only authorised users and authorised external connecting Supplier Solutions can access the test environment.

All

TEST-ENV-12

The Supplier shall ensure that the performance of the test Solution is comparable to the LIVE service levels for the restricted volumes in the Test environment, in order to provide a realistic expectation of performance behavior in the LIVE estate.

All

TEST-ENV-13

The Supplier must provide any necessary documentation pertaining to external interfaces to allow the integration of connecting systems.