New User having trouble -- tests fail
See original GitHub issueI am having trouble getting tests to pass with master branch
setup
conda create -n test-proxy jupyter python=3.7 tornado=5 pytest
conda activate test-proxy
pip install -e . # master of jupyter-server-proxy
JUPYTER_TOKEN=secret jupyter-notebook --config=./tests/resources/jupyter_server_config.py &
py.test tests/
The only test which passes is test_utils.py
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
What To Do When Tests Fail? - TestProject
What Should I Do When a Test Fails? ... Tests usually fail due to server and network issues, an unresponsive application or validation...
Read more >How to Fix Flaky Tests
Randomly failing tests are the hardest to debug. Here's a framework you can use to fix them and keep your test suite healthy....
Read more >Why users fail. Frequent usability issues we have observed ...
A list of some difficulties that have been repeating in most usability tests, regardless of the business sector, device used or participants' skills....
Read more >Test Automation Best Practice #6: Resolve Failing Test ...
This article focuses on the 28% of test failures that result from issues such as missing or invalid test data, problems with the...
Read more >ruby on rails - User update test fails when more users present
I've tested and it looks like the patch request is failing, and the user name and email are the original user name and...
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
The
-e
, I believe, is comparable tosetup.py develop
. That is, making things editable from the source directory. But that worked! Thanks @manics !!!Sure, a note seems reasonable. I think we should probably document this behavior in the
notebook
repository, since it’s pretty easy to run into this when developing server extensions.