EX46: nosetests ran 0 tests or ran 1 tests with Error

Python
#21

Wait, what? So on windows would you say this is the test procedure:

  1. Create ex47/tests/__init__.py file.
  2. Create ex47/ex47/__init__.py file.
  3. Create ex47/tests/simple_test.py and have it import ex47.game.
  4. nosetests runs nothing.
  5. Delete ex47/tests/__init__.py file.
  6. nosetests runs simple_test.py.

If that’s true I have questions:

  1. Why are all your paths in this “ex47/”? Are you inside that directory or above it?
  2. Is there a way you can craft up two directories with just this as a demo? One nosetests fails and one that it runs in? If you can then I’d love to get it to figure out what’s going on.
#22

@zedshaw Yes. That’s exactly the steps.

My environment is Windows 10 64bit, Python 3.8.1, nosetests version 1.3.7, PowerShell version 5.1.18362.752.

I’m always running nosetests from the root of the project directory as shown below.
This is my initial result after completing exercises 46 & 47 with problem file shown:
C:\USERS\HAWK_FW\PYTHON\PROJECTS\EX47
│ setup.py
│
├───bin
├───docs
├───ex47
│ │ game.py
│ │ __init__.py
│ │
│ └───__pycache__
├───tests
| │ ex47_tests.py
| │ __init__.py <-------Problem File
| │
| └───__pycache__

(lpthw) PS C:\Users\Hawk_fw\python\projects\ex47> nosetests

----------------------------------------------------------------------
Ran 0 tests in 0.007s

OK

As requested I created two new projects and tested them. The first one works and the second one fails.

First test:
C:\USERS\HAWK_FW\PYTHON\PROJECTS\TEST01_WORKS
│ setup.py
│
├───bin
├───docs
├───ex47
│ │ game.py
│ │ __init__.py
│ │
│ └───__pycache__
├───tests
| │ ex47_tests.py
| │
| └───__pycache__
(lpthw) PS C:\Users\Hawk_fw\python\projects\test01_works> nosetests
...
----------------------------------------------------------------------
Ran 3 tests in 0.016s

OK

Second test:
C:\USERS\HAWK_FW\PYTHON\PROJECTS\TEST02_DOES_NOT_WORK
│ setup.py
│
├───bin
├───docs
├───ex47
│ │ game.py
│ │ __init__.py
│ │
│ └───__pycache__
├───tests
| │ ex47_tests.py
| │ __init__.py
| │
| └───__pycache__
(lpthw) PS C:\Users\Hawk_fw\python\projects\test02_does_not_work> nosetests

----------------------------------------------------------------------
Ran 0 tests in 0.016s

OK

I’d be happy to send you both project test directories and files if you have an upload location and format preference.

#23

That’s so weird. Why in the world would that cause nostests to fail like that?

If you are into using the better new testing thing, then replace nose with https://docs.pytest.org/en/latest/

#24

Pytest works great! Thanks for the suggestion; I’ll keep using it in favor of nose.

The only change I had to make was to change the name of the test file from *_tests.py to *_test.py and pytest worked straight out of the box.

1 Like
#25

I had the same problem described by the OP. Resolved by moving the NAME_tests.py out of the tests directory into the skeleton directory. Will switch to pytest.

Thank you.

#26

image

I also have this problem with nosetests running 0 tests.

I have removed the init.py file from ./skeleton/tests, and this returns an error BUT it runs 1 test. When I create the init.py file in ./skeleton/tests, ‘nosetests’ runs 0 tests.

Has a solution to this problem been found?

I have checked that the venv directory contains the script nosetests (it does). I have checked that .venvs/lpthw/Lib/site-packages/nose/tools contains scripts to import. I have tried running nosetests from all levels of the directory with no luck. I have carefully repeated the entire exercise multiple times.

Edit: I tried moving NAME_tests.py to the parent directory, ./skeleton/, and this successfully runs 1 test, BUT only when I run nosetests from ./skeleton. It does not run a test when I run it from ./skeleton/tests. This makes sense, but I am not sure why it would not run when NAME_tests.py when it was in ./skeleton/tests.

I am genuinely stuck…

#27

Honestly, the best way to unstuck yourself is by switching to Pytest. You are wasting your time with Nose.

#28

Thanks for the suggestion! I will switch once I reach that point in the book, and from what I’ve read, continue to use it for that point forwards.

#29

I agree with that. Nose has died since I wrote the book and pytest is just easier.

#30

Thanks to @florian issue was resolved (by switching to pytest, lol). Not sure, at least now, how to properly read its output though.

Mr. @zedshaw since tool described in your book is obsolete now, maybe it will be helpful to create and pin a post about Pytest and basics of it’s usage? Like you pinned a forum rules.
Sort of “appendix” to ex.46.

#31

I would if I had time but I’ve honestly been moving on Python entirely because of these very problems. If I ever finish my other work I’ll consider a rewrite of Python.

#32

Thanks bro
The way you suggested worked for me as well