Which test document is required according to Automotive SPICE®?

According to the Automotive SPICE® (ASPICE) Process Assessment Model, testing processes such as SWE.5 (Software Integration and Integration Test) and SWE.6 (Software Qualification Test) require the development of a test specification. This test specification (Work Product 17-50) must contain test cases designed to verify the software. A fundamental part of a test case is the procedure for its execution, which details the sequence of actions. Therefore, a "Test procedure specification," which documents these execution steps, is a required artifact to fulfill the base practices (e.g., SWE.6.BP2: Develop software qualification test specification) of the model.

B. A specific "Test management report" is not a formally mandated work product by the ASPICE testing processes, though test status is reported.
C. While metrics are essential for process capability, a distinct "Test metrics report" is not a required work product; results are part of the standard test report.
D. Load testing is a specific type of non-functional testing; ASPICE does not mandate this specific test type or its corresponding report for all projects. ---

1. Automotive SPICE® Process Assessment Model, Version 3.1 (2017). VDA Quality Management Center (QMC).

Section: Software Engineering Process Group (SWE), specifically processes SWE.5 and SWE.6.

Details: Base Practice SWE.6.BP2, "Develop software qualification test specification," requires the creation of Work Product 17-50 "Test Specification." The characteristics of this work product are defined to include "Test cases" and "Test procedures for executing the test cases," which directly corresponds to a test procedure specification.

2. Fünger, N., & GrGens, G. (2018). Basiswissen Automotive SPICE®. dpunkt.verlag.

Chapter: 4, Software Engineering Prozesse (SWE).

Details: The book, explaining the practical application of ASPICE, clarifies that the test specification required by processes like SWE.5 and SWE.6 must detail the test cases, including their preconditions, input data, and step-by-step execution procedures to ensure repeatability and verifiability, which is the definition of a test procedure specification.