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

Fix System test type in breeze #43670

Merged
merged 2 commits into from
Nov 5, 2024

Conversation

o-nikolas
Copy link
Contributor

Adjust the behaviour of the System test type in Breeze testing tests. Remove the path appending to the beginning of the breeze command (because as we've discussed before with the reorganization of our test directories this creates a non-top level loading of a pytest plugin which pytest disallows). This allow us to still specify the System test type because that option controls other beahviours we need (like disabling db init).


^ 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.rst or {issue_number}.significant.rst, in newsfragments.

Adjust the behaviour of the `System` test type in Breeze testing tests.
Remove the path appending to the beginning of the breeze command
(because as we've discussed before with the reorganization of our test
directories this creates a non-top level loading of a pytest plugin
which pytest disallows). This allow us to still specify the System test
type because that option controls other beahviours we need (like
disabling db init).
@potiuk
Copy link
Member

potiuk commented Nov 5, 2024

The "standard" python issue with docs is caused by unrelated issue, we will fix it separately.

Yeah - it looks like a good band-aid for now. I will fix it during #42632 (I already have a draft). I will also add a separate test to test sytem tests in CI as part of it, so that it will not happen in the future

@potiuk potiuk merged commit 90b9847 into apache:main Nov 5, 2024
75 of 77 checks passed
sunank200 pushed a commit to astronomer/airflow that referenced this pull request Nov 5, 2024
* Fix System test type in breeze

Adjust the behaviour of the `System` test type in Breeze testing tests.
Remove the path appending to the beginning of the breeze command
(because as we've discussed before with the reorganization of our test
directories this creates a non-top level loading of a pytest plugin
which pytest disallows). This allow us to still specify the System test
type because that option controls other beahviours we need (like
disabling db init).

* Fix unit test
topherinternational pushed a commit to topherinternational/airflow that referenced this pull request Nov 5, 2024
* Fix System test type in breeze

Adjust the behaviour of the `System` test type in Breeze testing tests.
Remove the path appending to the beginning of the breeze command
(because as we've discussed before with the reorganization of our test
directories this creates a non-top level loading of a pytest plugin
which pytest disallows). This allow us to still specify the System test
type because that option controls other beahviours we need (like
disabling db init).

* Fix unit test
ellisms pushed a commit to ellisms/airflow that referenced this pull request Nov 13, 2024
* Fix System test type in breeze

Adjust the behaviour of the `System` test type in Breeze testing tests.
Remove the path appending to the beginning of the breeze command
(because as we've discussed before with the reorganization of our test
directories this creates a non-top level loading of a pytest plugin
which pytest disallows). This allow us to still specify the System test
type because that option controls other beahviours we need (like
disabling db init).

* Fix unit test
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