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

Re-arrange test configurations #721

Open
Paul-Ferrell opened this issue Dec 1, 2023 · 0 comments
Open

Re-arrange test configurations #721

Paul-Ferrell opened this issue Dec 1, 2023 · 0 comments

Comments

@Paul-Ferrell
Copy link
Collaborator

Currently tests are organized into a single tests directory, and their source is generally expected to be in the test_src. This makes keeping source and tests organized as a single unit difficult.

Re-organize tests/test_src such that:

  • test_src and tests are optional (and no longer created when setting up config areas.
  • Suite configs in tests/ at the top level still work as per-current mechanisms, but are deprecated.
  • A new suites directory is created by default instead.
    • Suites can exist as just a <suite_name>.yaml, but such suites should not have any locally provided source (downloads are fine though).
    • Suites are expected to be in a directory that determines the suite name.
    • A suite.yamlfile should exist in each directory that contains the Pavilion config for that suite.
    • Source paths are relative to the suite's directory.
    • The . source path should copy the suite directory (except the suite.yaml file, which shouldn't count towards the build hash).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant