PR: Fix Pytest catching up tests using Spyder-unittest or VSCode #20092
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.
Description of Changes
When Debugging in an editor with pytest support (for example spyder with spyder-unittest plugin, PyCharm or VS Code) the tests were not catched up.
This was due to the fact that there was
E ImportError: QtWebEngineWidgets must be imported or Qt.AA_ShareOpenGLContexts must be set before a QCoreApplication instance is created
Defining 'pytest_plugins' in a non-top-level conftest is no longer supported:
Both is fixed in this commit allowing to run a single Test file directly from the IDE or even debugging a single test directly.
Before that, one could only run a single test using
pytest testfile.py
instead of the whole suiteAffirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.
I certify the above statement is true and correct: Florian Maurer