Make tests runnable in empty environment
See original GitHub issueRight now, if you install holoviews, install nose, and then try running the holoviews tests with nosetests --with-doctest -v
, there are 18 failures (and pages of associated output) because of not having iris, flexx, plotly, and other optional libraries installed:
FAILED (SKIP=56, errors=407, failures=18)
This makes it very difficult to determine if the basic holoviews installation is working, particularly if you want to see if it works well without those optional libraries. Is it just a matter of needing to raise 18 more SkipTest exceptions?
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (7 by maintainers)
Top Results From Across the Web
How to test code dependent on environment variables using ...
The usual solution is to create a class which manages the access to this environmental variable, which you can then mock in your...
Read more >Dealing with Environment Variables while running Unit Tests
This blog will cover how to test code on a CI pipeline that reads variable from environment. CI pipeline run before deployment. So,...
Read more >Unit test with Set Environment Variables is running fine in my ...
In my unit test, I am setting the environment variables using stefanbirkner library. In local it is working fine. but when build it...
Read more >How to set "default" environment variables?
Please, go to `Run| Edit Configurations| Defaults| Python tests| Unitests/Nosetests/...` and specify your environment variables in "Environment ...
Read more >How To Setup JUnit Environment For Your First Test?
Add JUnit to the classpath: set CLASSPATH=%CLASSPATH%;%JUNIT_HOME%\junit.jar. Do JUnit tests run in parallel? Yes, JUnit by default runs tests ...
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 FreeTop 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
Top GitHub Comments
Thanks! There is plenty of interest inside Anaconda in tox+conda, both in my own group and from the conda maintainers. My own group (PyViz) would be happy to test it out and provide fixes for any problems we can figure out, and I think the conda team will be able to help us with any deeper issues that come up…
For reference: progress will be tracked in the already above mentioned issue (https://github.com/tox-dev/tox/issues/273).