summaryrefslogtreecommitdiff
path: root/tests/coveragetest.py
Commit message (Collapse)AuthorAgeFilesLines
* style: use good style for annotated defaults parametersNed Batchelder2023-01-051-24/+24
|
* mypy: Iterator is better than GeneratorNed Batchelder2023-01-051-2/+2
|
* mypy: use __future__ uniformly in checked filesNed Batchelder2023-01-051-0/+2
|
* mypy: test_coverage.py, test_data.pyNed Batchelder2023-01-041-3/+3
|
* mypy: summary.py, test_summary.py, tests/coveragetest.pyNed Batchelder2023-01-041-36/+86
|
* mypy: add cmdline.py and test_cmdline.pyNed Batchelder2022-12-311-2/+2
|
* refactor: removed mentions of Jython and IronPythonNed Batchelder2022-12-301-17/+3
|
* feat: implicit path mapping during reporting. #1212Ned Batchelder2022-11-271-1/+4
|
* test: a utility print for when reporting tests failNed Batchelder2022-11-021-0/+1
|
* build: Build and test tweaks to help with cross-compilationSteve Dower2022-04-301-1/+6
| | | | | | | | | | | | | | | For context, I've been testing whether a range of popular libraries are going to work on Windows ARM64. (This requires compiling on a regular x64 machine and then copying the wheel to an ARM64 one for testing.) The good news is, coverage seems to be just fine without any changes. However, because of a few assumptions in the test suite about always testing an in-place build, I had to make some tweaks to be able to run tests. My proposed tweaks should be fine for current uses, but they also allow the following: * support `SETUPTOOLS_EXT_SUFFIX` when building to override the pyd tag on Windows (used with `setup.py build_ext -L <path>` to point at [pythonarm64](https://www.nuget.org/packages/pythonarm64/) import libraries to do the cross-compile) * allow `COVERAGE_INSTALL_ARGS` to override how the tests install coverage into a venv (allows to point at a wheel rather than rebuilding from the sources) * allow `python igor.py remove_extension --from-install` to delete the extension module from `site-packages` rather than only the source tree * other changes to allow removing the `coverage` directory from the source tree before tests so that the installed copy will be used instead. I've tested these on my own Windows ARM64 machine, though unfortunately there aren't any available on CI services yet. If you wanted to start releasing (preview) wheels for win-arm64 you can, but there's no support (yet) in `cibuildwheel` or `build` to do it (because those tools don't really have a concept of cross-compilation for Windows at all... yet ;-) ). For the linter
* refactor(test): make_data_file is a helper for making data filesNed Batchelder2021-11-201-0/+10
|
* style: convert more string formatting to f-stringsNed Batchelder2021-11-111-4/+2
|
* refactor(test): use the expected name for initializing tests.Ned Batchelder2021-11-071-4/+4
| | | | | | | | | 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.
* test: we don't need two sys.path restorersNed Batchelder2021-10-141-2/+2
|
* test: don't use subprocesses where we don't have toNed Batchelder2021-10-131-0/+11
| | | | | | When running tests with `-n 0`, this shaves 4 seconds off the run time. When running the complete test suite with xdist, it takes 2 seconds longer!?
* refactor: move a test helper to CoverageTestNed Batchelder2021-08-141-0/+8
|
* test: don't report this function in pytest tracebacksNed Batchelder2021-07-201-0/+1
|
* test: change how we keep mismatched actual outputNed Batchelder2021-07-151-9/+0
| | | | | | | | | | | | Now when a goldtest has a failure, the actual mismatched output will be written to the tests/actual directory. Along the way, I removed some obsolete settings which were only used by unittest and unittest_mixins, which we no longer use: - COVERAGE_KEEP_TMP - COVERAGE_ENV_ID - $TMPDIR/coverage_test
* test: hide check_coverage source in pytest tracebacksNed Batchelder2021-06-041-0/+2
| | | | | | | The code for the helper is uninteresting and long, and only makes it harder to see what is going wrong. Hide it. https://docs.pytest.org/en/latest/example/simple.html#writing-well-integrated-assertion-helpers
* refactor: pyupgrade --py36-plus tests/**.pyNed Batchelder2021-05-021-13/+13
|
* refactor: move the remaining backward.py code, no more backward.pyNed Batchelder2021-05-011-1/+1
|
* refactor: remove unneeded backward.py shimsNed Batchelder2021-05-011-4/+5
| | | | | | | | | | | | | | | Removed were: - StringIO - configparser - string_class - unicode_class - range - zip_longest - get_thread_id - path_types - shlex_quote - reprlib
* refactor: nice_file can be used as a functionNed Batchelder2021-03-221-13/+8
|
* refactor: pull module cleaning into hereNed Batchelder2021-03-111-13/+3
| | | | We don't need unittest_mixins' module cleaner anymore.
* test: simplify how StopEverything is converted to skipnedbat/remove-unittest-testcaseNed Batchelder2021-03-111-5/+1
| | | | | | The auto-decorating metaclass was interfering with parameterized methods on Python 2.7. But we don't need it anymore anyway, since pytest will let us hook to deal with the exception in a simpler way.
* refactor: no need for our own xfail wrapperNed Batchelder2021-03-111-5/+0
|
* test: reduce use of unittestNed Batchelder2021-03-111-14/+16
|
* refactor: no need for specialized assert_starts_with methodNed Batchelder2021-03-061-5/+0
|
* refactor: replace unittest_mixins.EnvironmentAwareMixin with a pytest adapterNed Batchelder2021-03-041-2/+2
|
* test: add tests of the failure asserts from check_coverageNed Batchelder2021-02-221-3/+3
| | | | This brings the coverage of tests/coveragetest.py to 100%.
* refactor: slightly better coverage in coveragetestNed Batchelder2021-02-211-3/+3
|
* refactor: convert all skipping to pytest skipsNed Batchelder2021-02-071-1/+1
|
* refactor: remove unittest.assertCountEqualNed Batchelder2021-02-061-4/+4
| | | | Another step toward removing unittest.TestCase.
* refactor: remove reliance on unittest_mixins.StdStreamCapturingMixinNed Batchelder2021-02-021-2/+2
| | | | This is another step toward removing unittest.TestCase as a base class.
* refactor: move test mixins to their own fileNed Batchelder2021-02-021-29/+3
|
* test: keep multi-assert arc diffs workingNed Batchelder2021-01-311-23/+23
| | | | | We don't have a way to do multi-assert in the pytest we're running, so cobble it together ourselves.
* style: fix long lines and avoid backslashesnedbat/unittest2pytestNed Batchelder2021-01-311-1/+2
|
* refactor: mark an internal methodNed Batchelder2021-01-311-4/+4
|
* test: adapt to pytest assertion messagesNed Batchelder2021-01-311-4/+4
| | | | | | | | Bare "assert" statements don't produce the same assertion message as self.assertEqual did: they don't include the two values compared. For some of our own asserts, add back the detailed message. For some checks of asserts, it's fine that the values are missing because the longer messsage includes the information.
* refactor: unittest2pytest -w testsNed Batchelder2021-01-311-12/+12
| | | | One step of moving to pure pytest tests.
* PEP 626: constant tests are kept as no-opsNed Batchelder2021-01-101-1/+1
| | | | | The conditionals are now getting unwieldy, perhaps we can simplify them in the future?
* In 3.10, modules always have firstlineno==1Ned Batchelder2021-01-101-0/+5
|
* Explain a mysteryNed Batchelder2020-09-021-0/+4
|
* Better xfail mechanismNed Batchelder2020-01-181-4/+5
|
* Move test helpers to tests.helpersNed Batchelder2019-12-311-1/+2
|
* Easier to decipher arcz outputNed Batchelder2019-12-311-3/+3
|
* Warnings can be marked to only display once.Ned Batchelder2019-12-271-1/+2
|
* bpo 39114 broke 3.9, but maybe it's their bugNed Batchelder2019-12-211-0/+5
|
* I'm not sure why I was deleting these meta env varsNed Batchelder2019-12-011-7/+0
| | | | Don't we want to measure the coverage of subprocesses we start in tests?
* Coverage.py is only capitalized when it starts a sentenceNed Batchelder2019-11-101-3/+3
|
View Lorry Controller Status