Documentation tests are no longer run by default
See original GitHub issueWhile trying to get pytest 3.x to work (#5688), I noticed that some of the rst
files do not pass even with current master (i.e., the built-in pytest). The problem seems to be that currently none of the doctests get run. E.g., a recent travis log [1] shows only test files, while older ones also show regular python files with doctests as well as the rst files [2]. So, somehow they are getting omitted… (or am I missing something totally dumb???)
[1] recent log, no doctests: https://travis-ci.org/astropy/astropy/jobs/191377361 [2] older log, includes doctests: https://travis-ci.org/astropy/astropy/jobs/158108205
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Run tests | IntelliJ IDEA Documentation - JetBrains
Run the selected test or test folder: Ctrl+Shift+F10. Stop the current test ... For more information, refer to Run/debug configurations.
Read more >unittest — Unit testing framework — Python 3.11.1 ...
You can run tests with more detail (higher verbosity) by passing in the -v flag: python -m unittest -v test_module. When executed without...
Read more >Running tests through command-line with run-tests.sh - Drupal
Required when running tests without a Drupal installation that contains default database connection info in settings.php.
Read more >VSTest@2 - Visual Studio Test v2 task - Microsoft Learn
You can run test frameworks that have a Visual Studio test adapter. ... Default: $(test.RunId). ... Fail the task if a minimum number...
Read more >Migration Guide | Cypress Documentation
Migrating to Cypress 12.0 This guide details the changes and how to change your code to migrate to Cypress version 12.0.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Just as I suspected… https://travis-ci.org/astropy/astropy/jobs/190406534 does not have doctest for the first time. I think the mistake here is introducing pytest 3.x feature in #5678, which is not ready for the transition yet. It was necessary for testing with pytest 3.x locally (at the hack day) but it should not be propagated to master until bundled version is removed. I propose changing
[tool:pytest]
back to[pytest]
in current master and re-introduce the change in #5688. What do you think?@pllim - nice tracking down! I agree we need to undo the change in
setup.cfg
.