Skip to main content

Test

The system and products are integrated and tested to provide stakeholders with information about the quality of potential deliverables or releases.

Testing on software and hardware levels (unit and component tests) is described in the respective processes software process, and hardware process.

Security testing is a part of testing at all levels. For more information about Security testing, see 3BSE070423 Security Testing Guideline.

Process Overview​

Principles​

  • Each stream/release shall establish a test strategy that details the test activities based on specific needs. The test strategy should be documented as part of the Test Strategy and Plan Document.
  • Strive for automated tests, when possible, to reduce manual and repetitive work.
  • Continuously integrate and test to find bugs early and fail fast.
  • Product tests shall ensure the epic's acceptance criteria are fulfilled.
  • System tests shall ensure that system epics acceptance criteria are fulfilled.
  • Test performance and scalability and identify potential vulnerabilities.
  • Summarize the final performed tests and conclusions in a test report.

Activities​

Test1

Artifacts​

ArtifactDescription​RACI​Receiver​Comments
Product test strategy and planTest strategy and plan for a product release (including the needs for test environments and test applications).​(R): Test Lead
(A): Stream Owner
(C): Architect, Cyber Security Engineer, Development Team, Ex Representative, Product Owner, Quality Control Manager, Release Owner, Test team
(I): 3rd party SW engineer, Configuration Manager, Product Manager		Dev. Team​The format can be decided per stream.​
Product test case​Test cases executed in the Product Test Environment. ​(R): Test team
(A): Test Lead
(C): Cyber Security Engineer, Test team
(I): Development Team, Product Owner		Dev. Team​-
Product test result​The outcome of executed test cases is documented in the test tool.​ Only the final test result is reviewed and approved.(R): Test team
(A): Product Owner
(C): Test Lead
(I): Cyber Security Engineer, Quality Control Manager, Release Owner​		Dev. Team​-
Product test report​A report summarizing qualitatively and quantitatively the outcome of the tests.​(R): Test Lead
(A): Stream Owner
(C): Product Owner, Release Owner, Test team
(I): Cyber Security Engineer, Development Team, Quality Control Manager, Product Manager		Product Owner-
Product test environmentDescription of the product test environment.(R): Test team
(A): Test Lead
(C): Architect, Configuration Manager, Product Owner
(I): Cyber Security Engineer, Product Manager		Dev. TeamThe test environment can be included in the test strategy for smaller configurations.
Product test applicationsProduct test applications needed to execute tests.(R): Test Team
(A): Test Lead
(C): -
(I): -		Dev. TeamThe test applications are part of the test environment and are managed as code.
System test strategy and planTest strategy and plan for a system release (including the needs for test environment and test applications).​(R): Test Lead
(A): Stream Owner
(C): Architect, Cyber Security Engineer, Quality Control Manager, Release Owner, Test team, Product Manager
(I): 3rd party SW engineer, Configuration Manager, Product Owner, Technical Coordinator		Dev. Team​The format can be decided per stream​.
System test case​Test cases executed in the System Test Environment. ​(R): Test team
(A): Test Lead
(C): Technical Coordinator, Test team, Product Manager
(I): Product Owner		Test Team​-
System test result​The outcome of executed test cases is documented in the test tool or a separate artifact.​ Only the final test result is reviewed and approved.(R): Test team
(A): Test Lead
(C): -
(I): Cyber Security Engineer, Product Owner, Quality Control Manager, Release Owner, Product Manager		Test Lead-
System test report​A report summarizing qualitatively and quantitatively the outcome of the test.​(R): Test Lead
(A): Stream Owner
(C): Test team, Product Manager
(I): Cyber Security Engineer, Product Owner, Quality Control Manager, Release Owner, Technical Coordinator		Test TeamThe test environment can be included in the test strategy for smaller configurations.
System test environmentDescription of system test environment.(R): Test team
(A): Test Lead
(C): Architect, Product Manager
(I): Cyber Security Engineer, Product Owner, Technical Coordinator		Test Team-
System test applicationsThe system test applications that are needed to execute tests.(R): Test Team
(A): Test Lead
(C): -
(I): -		Test TeamThe test applications are part of the test environment and are managed as code.
Note: Cyber Security, Safety, and Ex roles should be considered when applicable.

Dependencies​

Test2

References​

Owner: Test Team