Skip to content

Deduplicate system test entries in tests.yaml#775

Open
PranjalManhgaye wants to merge 1 commit into
precice:developfrom
PranjalManhgaye:fix-767-deduplicate-tests-yaml
Open

Deduplicate system test entries in tests.yaml#775
PranjalManhgaye wants to merge 1 commit into
precice:developfrom
PranjalManhgaye:fix-767-deduplicate-tests-yaml

Conversation

@PranjalManhgaye
Copy link
Copy Markdown
Contributor

Summary

This PR addresses #767 by reducing duplication in " tools/tests/tests.yaml" , We use YAML anchors and aliases for tutorial entries that appear in multiple test suites. The resolved test configuration stays the same, but the file becomes shorter and easier to maintain when we need to update shared tutorial entries later.

What changed
  • Added YAML anchors for repeated tutorial entries.
  • Replaced duplicated entries with YAML aliases.
  • Kept the same test suites, tutorial paths, case combinations, and reference result paths.

Why

Before this change, we had the same tutorial entries repeated in several suites. If we wanted to update one shared entry later, we would have to remember to update every copy. With this change, we define the repeated entries once and reuse them where needed. This should make future maintenance simpler without changing how the system tests behave.

Validation

I checked that this only changes the YAML structure, not the resolved test configuration.
Ran locally:
bash
git diff --check python3 -m compileall tools/tests python3 tools/tests/systemtests.py --help
I also compared the parsed tests.yaml against upstream/develop; both resolved to the same 13 test suites and 37 tutorial entries.

Checklist:

  • I added a summary of any user-facing changes (compared to the last release) in the changelog-entries/<PRnumber>.md.
  • I will remember to squash-and-merge, providing a useful summary of the changes of this PR.

Use YAML anchors and aliases for repeated tutorial entries to keep the system test configuration easier to maintain without changing the resolved test suites.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants