Release 4.5.0#5246
Merged
Merged
Conversation
Co-Authored-By: Zac-HD <Zac-HD@users.noreply.github.com>
Pre-PR for warnings on unknown markers
So that we can ignore it in self-tests.
Emit warning on unknown marks via decorator
Split out list of essential plugins
…g_at_shutdown capture: do not set logging.raiseExceptions = False
Minor: doc, import
pdb: add option to skip `pdb.set_trace()`
…-code wrap_session: restore old behavior for initstate=1
run-last-failure: improve reporting
…to-features Merge master into features (with regen)
…5204) Emit a warning for record_property when used with xunit2
…ytest-dev#5221) Show fixture scopes with ``--fixtures``, except for "function" scope
We improve the following things in the logging format: * Show module name instead of just the filename * show level of logging as the first thing * show lineno attached to module:file details Thanks to @blueyed who suggested this on the github issue. It's my first contribution and I have added myself to AUTHORS. I also added to a changelog file.
logging: improve default logging format (issue5214)
Display message from reprcrash in short test summary
A lot of our examples use custom markers to make a point and showcase features, which generates a lot of warnings
Ignore PytestUnknownMark warning when generating docs
pdb: only use outcomes.exit via do_quit
It doesn't seem to add much value (why would one execute tests based on that marker?), plus using the docstring for that encourages one to write a more descriptive message about the test
Merge master into features
This exposes the functionality introduced in fa6acdc as a session-scoped fixture. Plugins that want to remain compatible with the `xunit2` standard should use this fixture instead of `record_property`. Fix pytest-dev#5202
Introduce record_testsuite_property fixture
Further "unknown marks warning" improvements
Codecov Report
@@ Coverage Diff @@
## master #5246 +/- ##
==========================================
- Coverage 96.06% 93.73% -2.34%
==========================================
Files 114 115 +1
Lines 25823 26159 +336
Branches 2550 2578 +28
==========================================
- Hits 24808 24520 -288
- Misses 705 1321 +616
- Partials 310 318 +8
Continue to review full report at Codecov.
|
Member
Author
|
Weird, the codecov is clearly incorrect: coverage was posted before Travis even started. |
Contributor
Seen this with some recent PR of mine also already - re-triggered the build a few times, but gave up then. |
blueyed
approved these changes
May 11, 2019
|
|
||
| - `#5023 <https://github.com/pytest-dev/pytest/issues/5023>`_: New flag ``--strict-markers`` that triggers an error when unknown markers (e.g. those not registered using the `markers option`_ in the configuration file) are used in the test suite. | ||
|
|
||
| The existing ``--strict`` option has the same behavior currently, but can be augmented in the future for additional checks. |
This file contains hidden or 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
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.

No description provided.