Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend general guidelines of conformance tests wrt to regression/unit tests #185

Closed
martinmo opened this issue Apr 29, 2024 · 0 comments · Fixed by #186
Closed

Extend general guidelines of conformance tests wrt to regression/unit tests #185

martinmo opened this issue Apr 29, 2024 · 0 comments · Fixed by #186
Assignees
Labels
SCS is continuously built and tested SCS is continuously built and tested in order to raise velocity and quality SCS is standardized SCS is standardized SCS-VP10 Related to tender lot SCS-VP10

Comments

@martinmo
Copy link
Member

martinmo commented Apr 29, 2024

Extend the guidelines created in #154 with information on regression/unit tests for the conformance tests (see SovereignCloudStack/standards#447 (comment)).

For completeness, the guidelines should also mention that the conformance checks should be executable with the least privileges possible, i.e., non-admin credentials for OpenStack and Kubernetes APIs and of course the scripts should never need root priveleges (this is already somewhat documented/standardized with scs-0004-v1).

@martinmo martinmo added SCS is continuously built and tested SCS is continuously built and tested in order to raise velocity and quality SCS is standardized SCS is standardized SCS-VP10 Related to tender lot SCS-VP10 labels Apr 29, 2024
@martinmo martinmo self-assigned this Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
SCS is continuously built and tested SCS is continuously built and tested in order to raise velocity and quality SCS is standardized SCS is standardized SCS-VP10 Related to tender lot SCS-VP10
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant