summaryrefslogtreecommitdiff
path: root/tests/test_process.py
Commit message (Collapse)AuthorAgeFilesLines
* refactor(test): convert eight tests to one parametrized testNed Batchelder2021-11-071-27/+4
|
* refactor(test): use the expected name for initializing tests.Ned Batchelder2021-11-071-6/+6
| | | | | | | | | Originally I used setup_test because something went wrong when I used setUp. I wrote https://github.com/pytest-dev/pytest/issues/8424 about it. There they say to use `-p no:nose` to disable nose interpretation. But now I simply went back to setUp, and all seems well? Not sure what changed, but using the expected name is better.
* refactor(test): make traceback checks a bit flexibleNed Batchelder2021-11-041-3/+6
| | | | | | | | | | | | Python 3.11 made a traceback look like this: Traceback (most recent call last): File "{path}", line 8, in <module> print(sys.argv[1]) ~~~~~~~~^^^ IndexError: list index out of range We needed to not care if that tilde-caret line was present or not.
* test(fix): isolate excepthook tests from each otherNed Batchelder2021-11-021-0/+2
|
* refactor(test): the virtualenv tests deserve their own fileNed Batchelder2021-10-311-263/+1
|
* refactor(test): make re_lines (et al) look like re.searchNed Batchelder2021-10-281-19/+19
| | | | and also replace some calls with just-plain re.search.
* refactor(test): re_lines is more useful if it returns a listNed Batchelder2021-10-271-6/+7
|
* feat: xml and json say what they are doing, and -q quiets everything. #1254nedbat/dashqNed Batchelder2021-10-261-2/+2
|
* fix: changes for PyPy3.8Ned Batchelder2021-10-251-1/+1
| | | | | | | | | | - Update tox.ini to let us run against PyPy3.8 - Some 3.8 behavior is (apparently) only on CPython - PyPy3.8 doesn't get along with virtualenv yet (https://github.com/pypa/virtualenv/issues/2182), so use venv instead for our virtualenv tests.
* refactor(test): os_sep and remove_tree helpersNed Batchelder2021-10-241-2/+2
|
* feat: `coverage run` now sets the COVERAGE_RUN environment variableNed Batchelder2021-10-161-1/+16
|
* test: very minor clean upNed Batchelder2021-10-161-1/+4
|
* fix: find_writable_pth_directory must expect failure from open()Michał Górny2021-10-121-4/+4
| | | | | | | Fix find_writable_pth_directory() to expect the OSError from the open() call. In general, this is what's going to happen if the file is not writable. The current logic could only be triggered e.g. if the file was writable but the underlying filesystem run out of space.
* test: add more tests of run_python_fileNed Batchelder2021-10-111-4/+7
| | | | | | The tests in test_process run the exception handling in execfile.py, but only under coverage, so metacov can't see it. These smaller tests exercise the code without coverage on top.
* fix: make third-party detection work with namespace packages. #1231Ned Batchelder2021-10-101-3/+74
|
* refactor: remove some left over test printsNed Batchelder2021-10-101-3/+0
|
* refactor: simplify some strange string formattingNed Batchelder2021-10-101-2/+2
|
* refactor: no need for maybe-u prefixes in test regexesNed Batchelder2021-10-101-2/+2
| | | | That was for Python 2, which we don't support anymore.
* style: prefer explicit string concatenationNed Batchelder2021-10-101-16/+15
|
* style: use the official designation for utf-8Ned Batchelder2021-10-101-1/+1
| | | | | Yes, this is completely unimportant. Don't ask me why I bothered, I'm not really sure.
* test: make metacov work with xdistNed Batchelder2021-10-081-1/+1
| | | | | | | | | I was using pytest.__file__ as a directory, but in 5.3.2, pytest changed to be a package, so that wasn't the site-packages directory anymore, and our .pth file was written someplace useless. Now we don't rely on the structure of pytest (why did we ever?), and it works again.
* feat: HTML report now says where the report is. #1195 (#1207)Ned Batchelder2021-08-051-2/+2
|
* fix: generate flat file names differentlyNed Batchelder2021-07-151-2/+3
| | | | | | | | Fixes a few unusual issues with reports: - #580: HTML report generation fails on too long path - #584: File collisions in coverage report html - #1167: Remove leading underscore in coverage html
* fix: --fail-under=100 could report 100 is less than 100.Ned Batchelder2021-05-311-0/+16
| | | | | | | Use the same rounding rules for the fail-under message that are used for totals everywhere else, so that it won't say: total of 100 is less than fail-under=100
* build: mark a few lines as not coveredNed Batchelder2021-05-301-2/+2
|
* feat: warnings are now real warningsNed Batchelder2021-05-301-5/+9
| | | | | | This makes coverage warnings visible when running test suites under pytest. But it also means some uninteresting warnings would show up in our own test suite, so we had to catch or suppress those.
* fix: Python 3.8.10 changed how __file__ is reported when running directoriesNed Batchelder2021-05-111-1/+1
|
* refactor: remove a few more version checksNed Batchelder2021-05-021-4/+1
|
* refactor: pyupgrade --py36-plus tests/**.pyNed Batchelder2021-05-021-41/+40
|
* refactor: remove code explicitly choosing between py2 and py3Ned Batchelder2021-05-011-16/+1
|
* fix: don't warn that dynamic plugins already imported their source files. #1150Ned Batchelder2021-05-011-1/+27
|
* fix: restore metacov functioningNed Batchelder2021-04-111-1/+1
| | | | | | | The check for coverage files inside the --source check disables our metacoverage. Removing it means that coverage files will still not be measured, but the reason will be given as "is third-party" rather than "is part of coverage.py," which is a small price to pay.
* fix: don't measure third-party scriptsnedbat/bin-excludeNed Batchelder2021-04-111-44/+111
| | | | | | This finishes the last bit of #905 Also includes tighter logging of the reason for not tracing modules.
* fix: don't measure third-party packagesNed Batchelder2021-04-101-1/+99
| | | | | | | | | | | | Avoid measuring code located where third-party packages get installed. We have to take care to measure --source code even if it is installed in a third-party location. This also fixes #905, coverage generating warnings about coverage being imported when it will be measured. https://github.com/nedbat/coveragepy/issues/876 https://github.com/nedbat/coveragepy/issues/905
* test: skip a test on pypyNed Batchelder2021-03-111-5/+4
| | | | | | I thought I knew when this passed and when it failed. Now that our tests are not TestCase's, pytest is enforcing the xfails. This passes locally on Mac, but fails in CI on Mac. So skip it.
* test: show more information for not-passed testsNed Batchelder2021-03-111-1/+1
|
* test: reduce use of unittestNed Batchelder2021-03-111-8/+7
|
* refactor: no need for specialized assert_starts_with methodNed Batchelder2021-03-061-1/+1
|
* build: update to latest pylintNed Batchelder2021-02-261-1/+1
|
* refactor: convert all skipping to pytest skipsNed Batchelder2021-02-071-37/+19
|
* test: these tests can run during metacovNed Batchelder2021-02-071-1/+0
| | | | I forget why I thought they couldn't run during meta-coverage.
* test: more-uniform skipping of test during metacovNed Batchelder2021-02-071-22/+13
|
* style: fix long lines and avoid backslashesnedbat/unittest2pytestNed Batchelder2021-01-311-11/+17
|
* refactor: unittest2pytest -w testsNed Batchelder2021-01-311-170/+162
| | | | One step of moving to pure pytest tests.
* Add combine --keep (#1110)Éric Larivière2021-01-301-0/+22
| | | | | | | | | | | * Add combine --keep Related to https://github.com/nedbat/coveragepy/issues/1108 * Fix unit tests * Fix line too long * Fix line too long
* Clean up the platform constants in env.pyNed Batchelder2021-01-101-1/+1
|
* Always output TOTAL line.Judson Neer2021-01-061-3/+9
|
* This test doesn't work on Mac either.Ned Batchelder2021-01-021-1/+1
|
* This test is picky about platformsNed Batchelder2020-11-281-1/+1
|
* Fix tests for GitHub windows platformNed Batchelder2020-11-281-3/+3
| | | | | | | | | | | | | | The tests were failing because of differences in file paths. It was comparing: C:\Users\runneradmin\AppData\... to: C:\Users\RUNNER~1\AppData\... and failing. These changes normalize the file paths so the comparisons work properly.
View Lorry Controller Status