Fix system-test pytest marker #32978
Merged
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.
We have an automated system-test pytest marker that applies the pytest.mark.system marker to all system tests. It has been implemented in a strange way as it was applying the marker to all provider tests if the whole "tests" directory was used for test collection.
This caused quarantine tests from providers folder to be skipped because they were automatically marked with pytest.mark.system marker.
Also system tests were generally excluded from running after we brought back the "test_*" prefix.
This PR updates the auto-marker to only apply system marker to tests in "system/providers" folder and adds the "example_*" prefix to the prefixes automatically collected by pytest.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.