SovereignCloudStack / SovereignCloudStack/standards

[Feature Request] Run tests in dedicated (write-once) directory

Open
#1,212 0 comments 1 reaction 1 assignee View on GitHub

@mbuechse is already working on this.

Since Jun 15, 2026.

enhancement
Dominant language
Python
Stars
47
Forks
38
Avg merge
1d 16h
Merged PRs (30d)
8

Description

We should introduce the concept of a results directory for a run. Either the user supplies one on the command-line, or one is created automatically (e.g., using subject, date, and time). This directory can later be used to diagnose problems with the tests. And tests then have a place for storing bigger log files etc.

The kaas tests already use a subject-specific directory for placing ephemeral kubeconfig.yaml during provisioning of the test cluster. Note that this directory is not specific to the run (even though it's currently abused also for results). However, we could copy its contents into the run-specific directory before the test is run: (a) so the test doesn't need to look at two different directories, and (b) to preserve its contents as part of the run's documentation.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.