tests: add pytest flags #38
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
svidiella
force-pushed
the
tests/add-pytest-flags
branch
2 times, most recently
from
1b62d88 to
ca759c5
Compare
svidiella
force-pushed
the
tests/add-pytest-flags
branch
from
1ba4216 to
1e7176a
Compare
|
@movsic take a look, please |
lkuligin
approved these changes
Feb 28, 2024
|
@efriis fyi, maybe you'll find the approach useful for the core repo |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add support for flags on pytest and use
--releaseflag for integration testsSupport of:
Flags can be combined, and a single test can be marked with several flags.
If no flags are provided, the test will be always executed.
If marked with a flag (e.g. @pytest.mark.release) the test will only be executed if the flag is specified in the pytest call.
Marked all currently not skipped integration tests as
release.Marked
test_llms_safetytests as extended (as they can be run normally in local, no extra CI setup seems to be needed).