Skip to main content

SCS end-to-end testing

Introduction​

From the beginning of the SCS project, it was always intended to reuse and include existing standards wherever appropriate, such as the Cloud-Native Computing Foundation's "Certified Kubernetes Conformance Program" or the OpenStack Interop working group's regulations regarding "OpenStack-powered Compute". Unfortunately, the latter has been retired in September 2025. This standard is meant to carry on the torch.

Motivation​

SCS operators as well as SCS users want to be sure that the infrastructure services work as expected.

Regulations​

The end-to-end testing is performed using Tempest.

The required tests are listed in Tests/iaas/scs_0128_e2e_testing/tempest-tests-non-admin.lst.

Tempest MUST NOT report any failed test cases.

Rationale​

In continuation of the original OpenStack-powered Compute, the list of Tempest test cases was extracted from 2022.11.json, the latest available guidelines file.

The following well-founded alterations were made:

  • testcases that require admin privileges were removed in line with general SCS principles,
  • tempest.api.identity.v3.test_users.IdentityV3UsersTest.test_user_account_lockout was removed because it is irrelevant in the most common scenario with an external identity provider. (decision)