Test Specification Guideline

Test Specification Guideline		status: valid
tags: verification contained by: wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test complies: std_req__iso26262__software_941, std_req__iso26262__software_942, std_req__iso26262__software_943, std_req__iso26262__support_9421, std_req__iso26262__support_9422, std_req__iso26262__support_9423, std_req__iso26262__support_9424, std_req__iso26262__software_app_c_42, std_req__iso26262__software_app_c_44, std_req__iso26262__software_app_c_45, std_req__aspice_40__iic-08-60
gd_guidl__verification_specification		Process Guideline

Test specification

A test specification contains the following attributes.

Table 54 Test specification properties

Property	Type / Values	Description	Helpful links
Partially and/or Fully Verifies	Docs-as-code Id(s) for traceable elements	Links to one or more requirement Ids. Can be partial or full coverage of a requirement, as per test property.
Description	Text	The description should include The objective of the test. Inputs Expected outcome (e.g. “A success message is displayed.”) Test environment (e.g. network configuration, clean system state)
TestType	Examples are: requirements-based interface-test coverage (various types apply, shall be tool supported)	These are example values and an incomplete list. A full list of test types is available in Verification Concept at Verification Methods.
DerivationTechnique	Examples are: requirements-analysis boundary-values equivalence-classes error-guessing	These are example values and an incomplete list. A full list of test methods is available in Verification Concept at Verification Methods.

The implementation of Verification Plan defines the full list of allowed types and methods.

Test description

Following Given-When-Then is a preferred way to write test specifications.

• Given (alternatively // Setup )

  This section contains the setup of the input.
• Expected

  This Section contains the expectation for calls to mocks or stubs
• When (alternatively // Call )

  This section contains the call to the software under test.
• Then (alternatively // Expect )

  This section contains the verification criteria of the test (e.g. all EXPECT statements).

TEST(CreateObjectHistory, GivenVehicleInFront_ExpectHistoryBehindFrontVehicle)
{
   // Given
   const auto whatever_input_values = CreateVehicleInFront();

   // Expected
   EXPECT_CALL(..., ...);

   // When
   const auto history = CreateObjectHistory(whatever_input_values, ...);

   // Then
   for (const auto point : history)
   {
      EXPECT_EQ(..., ...);
   }
}

Another example for a good test description could be:

Verify successful login with valid credentials.

Input:

- Username: testuser

- Password: password123

Expected Outcome:

- User is redirected to the home page and the welcome message “Hello, testuser!” is displayed.

A example for a bad test description could be:

Test user login

Additional information can also be found in Verification Guideline.

The specification is part of the test implementation and has to comply to the requirements specified in Linking Requirements to Tests.