a740ef2036
docs: Document doctest +NUMBER limitation with strings
...
Also added an "xfail" testcase for the same.
2019-07-11 10:06:57 +01:00
4c590e002f
Fix test_doctest.test_number_non_matches
...
These doctests were expected to fail, but they were failing because of a
silly bug (I forgot to replace "{expression}" with the actual expression
to be tested), not because of the thing they were meant to be testing.
Then I had to fix one of the testcases because it was actually matching:
>>> 3.0 #doctest: +NUMBER
2.99
The doctest is saying that the actual output should match to 2 decimal
places, i.e. within 0.01 -- which it is, so it passes. I changed the
expected output to 2.98 and now it doesn't match (as we expect).
2019-07-11 09:57:44 +01:00
d5cc0f2a62
changelog for new NUMBERS doctest option
2019-07-08 17:16:35 +01:00
2a23fdab9f
docs: Tidy up doctest options section
...
* Move the parts about "how to configure it" (pytest.ini vs. inline
comment) together.
* Move `--doctest-continue-on-failure` into its own sub-heading, as it
isn't related to the doctest optionflags.
2019-07-08 17:07:58 +01:00
aaa7e837cc
doctest: Add +NUMBER option to ignore irrelevant floating-point differences
...
When enabled, floating-point numbers only need to match as far as the
precision you have written in the expected doctest output. This avoids
false positives caused by limited floating-point precision, like this:
Expected:
0.233
Got:
0.23300000000000001
This is inspired by Sébastien Boisgérault's [numtest] but the
implementation is a bit different:
* This implementation edits the literals that are in the "got"
string (the actual output from the expression being tested), and then
proceeds to compare the strings literally. This is similar to pytest's
existing ALLOW_UNICODE and ALLOW_BYTES implementation.
* This implementation only compares floats against floats, not ints
against floats. That is, the following doctest will fail with pytest
whereas it would pass with numtest:
>>> math.py # doctest: +NUMBER
3
This behaviour should be less surprising (less false negatives) when
you enable NUMBER globally in pytest.ini.
Advantages of this implementation compared to numtest:
* Doesn't require `import numtest` at the top level of the file.
* Works with pytest (if you try to use pytest & numtest together, pytest
raises "TypeError: unbound method check_output() must be called with
NumTestOutputChecker instance as first argument (got
LiteralsOutputChecker instance instead)").
* Works with Python 3.
[numtest]: https://github.com/boisgera/numtest
2019-07-08 17:07:58 +01:00
60a358fa2d
Replace importlib_metadata with importlib.metadata on Python 3.… ( #5539 )
...
Replace importlib_metadata with importlib.metadata on Python 3.8+
2019-07-04 21:46:43 -03:00
c54cbd63c8
Replace importlib_metadata with importlib.metadata on Python 3.8+
...
Fixes https://github.com/pytest-dev/pytest/issues/5537
2019-07-04 15:00:10 +02:00
1db132290f
Apply workaround for multiple short options for Python <= 3.8
...
Hopefully by Python 3.9 this will be fixed upstream, if not we will
need to bump the version again.
Fix #5523
2019-07-04 14:59:40 +02:00
4f9bf028f5
Merge pull request #5522 from nicoddemus/merge-master-into-features
...
Merge master into features
2019-06-28 20:22:56 -07:00
4bc0415720
Merge pull request #5521 from asottile/cherry-pick-maintenance-release
...
4.6.4 changelog notes
2019-06-28 19:28:44 -07:00
844d660d5c
Merge pull request #5520 from asottile/release-4.6.4
...
Preparing release version 4.6.4
2019-06-28 19:09:10 -07:00
2c6453c72d
Merge pull request #5509 from asottile/release-5.0.0
...
Preparing release version 5.0.0
2019-06-28 18:12:16 -07:00
e6ffa78e59
Refactoring doctests ( #5518 )
...
Refactoring doctests
2019-06-28 19:15:02 -03:00
58bfc7736f
Use shutil.which to avoid distutils+imp warning
2019-06-28 14:44:49 -07:00
97f0a20ca9
Add notice about py35+ and move ExitCode changelog entry
2019-06-28 14:40:10 -07:00
55d2fe076f
Use importlib instead of imp in demo
2019-06-28 14:40:10 -07:00
5e39eb91bb
Correct Zac-HD's name in changelogs
2019-06-28 14:40:10 -07:00
fd2f320485
Preparing release version 5.0.0
2019-06-28 14:39:53 -07:00
73d918db55
Remove astor and reproduce the original assertion expression ( #5512 )
...
Remove astor and reproduce the original assertion expression
2019-06-28 18:36:11 -03:00
7ee244476a
Remove astor and reproduce the original assertion expression
2019-06-28 13:38:52 -07:00
bf39e89946
Refactoring doctests
2019-06-28 21:16:17 +02:00
3c9b46f781
Remove stray comment from tox.ini ( #5507 )
...
Remove stray comment from tox.ini
2019-06-27 15:12:57 -03:00
f7bfbb557e
Merge pull request #5506 from asottile/fix_no_terminal
...
Fix crash when discovery fails while using `-p no:terminal`
2019-06-27 10:46:43 -07:00
45af361a67
Remove stray comment from tox.ini
2019-06-27 10:46:08 -07:00
4e723d6750
Fix crash when discovery fails while using `-p no:terminal`
2019-06-27 10:24:29 -07:00
65fbdf2568
Don't crash with --pyargs and a filename that looks like a modu… ( #5503 )
...
Don't crash with --pyargs and a filename that looks like a module
2019-06-27 13:53:02 -03:00
5ef507982c
Add Open Collective to FUNDING.yml ( #5504 )
...
Add Open Collective to FUNDING.yml
2019-06-27 13:49:58 -03:00
2479a91e92
Add Open Collective to FUNDING.yml
2019-06-27 17:53:03 +02:00
3e0e31a364
Don't crash with --pyargs and a filename that looks like a module
2019-06-27 08:32:32 -07:00
c9923a3a5c
Merge pull request #5499 from nicoddemus/cleanup-py35-rewrite
...
Remove py<35 compatibility code from rewrite.py
2019-06-26 21:31:54 -07:00
1be49e713a
Remove py<35 compatibility code from rewrite.py
2019-06-26 21:44:10 -03:00
37fb50a3ed
Features assertion pass hook ( #3479 )
...
Features assertion pass hook
2019-06-26 21:14:19 -03:00
790806e865
Merge pull request #5494 from Zac-HD/funcargnames-to-fixturenames
...
Deprecate funcargnames alias for fixturenames
2019-06-26 21:13:59 -03:00
2ea22218ff
Cover assertions with messages when enable_assertion_pass_hook is enabled
2019-06-26 20:46:31 -03:00
629eb3ec6a
Move formatting variables under the "has impls" if
...
Small optimization, move the generation of the intermediate
formatting variables inside the 'if _check_if_assertion_pass_impl():'
block.
2019-06-26 19:26:12 -03:00
8edf68f3c0
Add a trivial note about astor
2019-06-26 19:21:12 -03:00
3afee36ebb
Improve docs and reference
2019-06-26 19:15:00 -03:00
fcbe66feba
Restore proper handling of '%' in assertion messages
2019-06-26 18:51:27 -03:00
eb90f3d1c8
Fix default value of 'enable_assertion_pass_hook'
2019-06-26 17:54:24 -03:00
6854ff2acc
Fixed import order pep8.
2019-06-26 19:05:17 +02:00
53234bf613
Added config back to AssertionWriter and fixed typo in check_if_assertion_pass_impl function call.
2019-06-26 19:00:31 +02:00
6f851e6cbb
Merge remote-tracking branch 'upstream/master' into features-assertion-pass-hook-master
...
# Conflicts:
# src/_pytest/assertion/rewrite.py
2019-06-26 18:12:56 +02:00
9a34d88c8d
Explanation variables only defined if failed or passed with plugins implementing the hook.
2019-06-26 18:10:16 +02:00
d91a5d3cd7
Further reverting changes.
2019-06-26 18:10:16 +02:00
f755ff6af1
Black formatting.
2019-06-26 18:10:16 +02:00
d638da5821
Using ini-file option instead of cmd option.
2019-06-26 18:10:16 +02:00
0fb52416b1
Reverted changes.
2019-06-26 18:10:15 +02:00
6a2d844c5d
Fix typo replace `circuting` with `circuiting`. ( #5497 )
...
Fix typo replace `circuting` with `circuiting`.
2019-06-26 11:09:22 -03:00
a48feb3261
Delete 5497.trivial.rst
...
Just a typo, no need for a changelog entry. :)
2019-06-26 11:09:04 -03:00
6cf8e71dca
Merge pull request #5496 from pytest-dev/stray_comment
...
Delete stray comment
2019-06-26 05:59:38 -07:00
David Röthlisberger
Bruno Oliveira
Miro Hrončok
Bruno Oliveira
Anthony Sottile
AmirElkess
Florian Bruhin
Victor Maryama