Add --junit-suite-name CLI option
#2273
Closed
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
…`Item` deriving from `PyobjMixin`
…rdance to PEP-479 Fix #2160
Replace 'raise StopIteration' usages in the code by 'return's in accordance to PEP-479
See #2231 for discussion.
…lobals 'xfail' markers without a condition no longer rely on the underlying `Item` objects deriving from `PyobjMixin`
Do not asssume `Item.obj` in 'skipping' plugin
KeyboardInterrupt is a subclass of BaseException, but not of Exception. Hence if we remove this except, KeyboardInterrupts will still be raised so the behavior stays the same.
Descriptors (e.g. properties) such as in the added test case are
triggered during collection, executing arbitrary code which can raise.
Previously, such exceptions were propagated and failed the collection.
Now these exceptions are caught and the corresponding attributes are
silently ignored.
A better solution would be to completely skip access to all custom
descriptors, such that the offending code doesn't even trigger. However
I think this requires manually going through the instance and all of its
MRO for each and every attribute checking if it might be a proper
fixture before accessing it. So I took the easy route here.
In other words, putting something like this in your test class is still
a bad idea...:
@Property
def innocent(self):
os.system('rm -rf /')
Fixes #2234.
ignore property errors when parsing fixure factories
…active Allow to skip unittests if --pdb active
Mention next training event.
As discussed in #2246
Improve pytest_plugins docs
--override-ini now correctly overrides some fundamental options like "python_files"
Python 3.6 invalid escape sequence deprecation fixes
Spelling fixes
Document pytest_report_header and conftest behavior
Simplify travis.yml with tox environment variables
In the xml report we now have two occurences for the system-out tag if the testcase writes to stdout both on call and teardown and fails in teardown. This behaviour is against the xsd. This patch makes sure that the system-out section exists only once per testcase.
junitxml: Fix double system-out tags per testcase
Update Changelog Update AUTHORS
|
Looks like i kind of messed up with master/feature base branches. I'll try to reopen it. |
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.
It can be used to control
<testsuite>'name' attribute. Resolves #533.