Skip to content

Commit 2b71d59

Browse files
committed
Adjust content after restructuring
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
1 parent 8a2e685 commit 2b71d59

2 files changed

Lines changed: 42 additions & 13 deletions

File tree

Standards/scs-0128-v1-e2e-test.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
title: SCS end-to-end testing
3+
type: Standard
4+
status: Draft
5+
track: IaaS
6+
description: |
7+
SCS-0128 describes standardized end-to-end testing. It was created to succeed
8+
the retired "OpenStack-powered Compute".
9+
---
10+
11+
## Introduction
12+
13+
From the beginning of the SCS project, it was always intended to reuse and include
14+
existing standards wherever appropriate, such as the Cloud-Native Computing Foundation's
15+
"Certified Kubernetes Conformance Program" or the OpenStack Interop working group's
16+
regulations regarding "OpenStack-powered Compute". Unfortunately, [the latter has been
17+
retired in September 2025](https://opendev.org/openinfra/interop).
18+
This standard is meant to carry on the torch.
19+
20+
## Motivation
21+
22+
SCS operators as well as SCS users want to be sure that the infrastructure services
23+
work as expected.
24+
25+
## Regulations
26+
27+
The end-to-end testing is performed using [tempest](https://docs.openstack.org/tempest/latest/index.html).
28+
29+
The required tests are listed in [Tests/iaas/scs_0128_e2e_test/tempest-tests-non-admin.lst].

Standards/scs-0128-w1-testing-notes.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,25 @@
11
---
2-
sidebar_label: Tempest Testing Project
2+
title: "SCS end-to-end testing: Notes"
3+
type: Supplement
4+
track: IaaS
5+
supplements:
6+
- scs-0128-v1-e2e-test.md
37
---
48

5-
# Tempest Testing Project
9+
## Tempest Introduction
610

711
Tempest is the OpenStack Integration Test Suite. It is a set of integration tests to be run against a live OpenStack cluster. Tempest has batteries of tests for OpenStack API validation, scenarios, and other specific tests useful in validating an OpenStack deployment.
812

9-
## Official documentation
13+
See also:
1014

11-
The official Tempest documentation is located on <https://docs.openstack.org/tempest/latest/>.
15+
- [Official documentation](https://docs.openstack.org/tempest/latest/)
16+
- [Current releases (with OpenStack/Python compatibility)](https://docs.openstack.org/tempest/latest/supported_version.html)
1217

13-
## Releases
18+
## Test cases
1419

15-
The current Tempest releases and their supported OpenStack releases and python versions can be found on <https://docs.openstack.org/tempest/latest/supported_version.html>.
16-
17-
## OpenStack Powered Compute test cases
18-
19-
As SCS conformance tests are expected to be executable without admin privileges (see §2 of
20-
[Regulations for achieving SCS-compatible certification](https://docs.scs.community/standards/scs-0004-v1-achieving-certification#regulations)), passing the following subset of OpenStack Powered Compute tests is sufficient to achieve _[SCS-compatible IaaS](https://docs.scs.community/standards/scs-compatible-iaas)_ compliance.
21-
22-
- [List of OpenStack Powered Compute non-admin tests](./tempest-tests-non-admin.lst)
20+
SCS conformance tests are expected to be executable without admin privileges (see §2 of
21+
[Regulations for achieving SCS-compatible certification](https://docs.scs.community/standards/scs-0004-v1-achieving-certification#regulations)).
22+
The list of test cases stated in the standard has ben curated accordingly.
2323

2424
## How to run Tempest against your cluster
2525

0 commit comments

Comments
 (0)