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

Use test-level tags in CI #850

Merged
merged 4 commits into from
Nov 29, 2024
Merged

Use test-level tags in CI #850

merged 4 commits into from
Nov 29, 2024

Conversation

bschimke95
Copy link
Contributor

Summary

Adds a test level to each integration test and use them in the CI

Rationale

The integration tests for each PR take way too long and test a lot of things that are very unlikely to break. It is sufficient to run those in the nightly test runs or even weekly (e.g. for conformance tests).

Changes

  • Assigns a test level to each integration test
  • ensures that the integration tests fail if a tag is missing for a test.
  • minor refactoring to ensure pull_request level tests and nightly tests are not in the same file
  • Use tags in the CI

Note that there is currently no weekly CI but I already added the tag for it. This is work for later.

Assigns a test level to each integration test and ensures that the integration tests
fail if a tag is missing for a test.
Also, enables the tags in the CI
@bschimke95 bschimke95 requested a review from a team as a code owner November 27, 2024 12:21
Copy link
Contributor

@eaudetcobello eaudetcobello left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very useful change, thanks!

Copy link
Member

@berkayoz berkayoz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Copy link
Contributor

@HomayoonAlimohammadi HomayoonAlimohammadi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work, thanks a lot @bschimke95! LGTM. Just minor comments and questions.
I'm not sure I fully understand which tag should be applied to which each test.
AFAIU, we mark the core/critical functionalities with PULL_REQUEST, less critical ones with NIGHTLY and even less critical ones with WEEKLY. Overall I think this is definitely the right direction and we can tune those tags as needed in the future.

tests/integration/tests/conftest.py Outdated Show resolved Hide resolved
tests/integration/tests/conftest.py Outdated Show resolved Hide resolved
tests/integration/tests/test_annotations.py Outdated Show resolved Hide resolved
tests/integration/tests/test_annotations.py Outdated Show resolved Hide resolved
tests/integration/tests/test_annotations.py Outdated Show resolved Hide resolved
Copy link
Contributor

@louiseschmidtgen louiseschmidtgen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for introducing the tags Ben, I've left a couple of opinions on pr/daily/weekly.

tests/integration/tests/conftest.py Outdated Show resolved Hide resolved
.github/workflows/nightly-test.yaml Show resolved Hide resolved
tests/integration/tests/test_etcd.py Show resolved Hide resolved
tests/integration/tests/test_strict_interfaces.py Outdated Show resolved Hide resolved
@bschimke95 bschimke95 merged commit eca8749 into main Nov 29, 2024
18 checks passed
@bschimke95 bschimke95 deleted the KU-2150/assign-test-levels branch November 29, 2024 09:14
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

Successfully merging this pull request may close these issues.

5 participants