question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Testing guideline page is obsolete and not built in main docs

See original GitHub issue

As per @rgommers’s advice, I am moving scipy/scipy#8606 to here.

The numpy testing guideline does not appear to be built with the other docs. It renders adequately on GitHub (https://github.com/numpy/numpy/blob/master/doc/TESTS.rst.txt), but seems out of place.

This is noticeable in particular because the scipy docs link to the GitHub page. The section on unit tests under the “Contributing New Code” section of the “Contributing to SciPy” page (http://scipy.github.io/devdocs/hacking.html#contributing-new-code) has a link to the “testing guidelines”, which points here.

Given that this page (probably among others) is important enough to link across projects, it would probably be a good idea to include it in the generated docs.

On top of the fact that the page is missing, it still refers to the old nose testing setup, and should probably be updated to include the switchover to py.test.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:1
  • Comments:18 (18 by maintainers)

github_iconTop GitHub Comments

1reaction
pvcommented, Apr 19, 2018

pip install -e pretty much requires virtualenv, otherwise it you’ll mess up your production environment.

1reaction
mattipcommented, Apr 19, 2018

It would be nice if someday we could move towards git clean -xfd; pip install -e . --upgrade ; pytest -m "not slow" for running tests in place, which works today. We should tweak our conftests.py so the slow tests are not run by default. IMO maintaining a runtests.py is a burden and can get in the way of the testing tool’s progress over time, but it will be a while till we can change this.

Pandas made the move to pytest recently, but their documentation still mentions nose testing. Maybe we could learn from their conftest.py and some of the pull requests marked with Testing and pytest

Edit: soften tone about runtests.py

Read more comments on GitHub >

github_iconTop Results From Across the Web

Experimental, deprecated, and obsolete - MDN Web Docs
On MDN Web Docs, the term obsolete was historically used to indicate an API or technology that is not only no longer recommended...
Read more >
Frontend testing standards and style guidelines - GitLab Docs
See the Testing Standards and Style Guidelines page for more information on general testing practices at GitLab. Vue.js testing. If you are looking...
Read more >
1995 Documentation Guidelines for Evaluation and ... - CMS
The documentation of each patient encounter should include: reason for the encounter and relevant history, physical examination findings, and prior diagnostic ...
Read more >
Snapshot Testing - Jest
Snapshot tests are a very useful tool whenever you want to make sure your UI does not change unexpectedly.
Read more >
Frequently Asked Questions | reCAPTCHA - Google Developers
Scores may not be accurate as reCAPTCHA v3 relies on seeing real traffic. For reCAPTCHA v2, use the following test keys. You will...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found