-w/--where does not preserve test selection by path

[jpellerin]

What steps will reproduce the problem?

1. create a suite with a subdirectory like "tests" and a file like
   tests/test_foobar.py
2. run $ nosetests --where=tests ./tests/test_foobar.py

What is the expected output? What do you see instead?

one would expect to have the test selected based on the file path but this
does not work since --where tells nose to chdir into the tests directory.

Workarounds :

This will work:
$ nosetests --where=tests test_foobar.py

The problem with that is you lose your shell's autocomplete ability :(

$ nosetests --where=tests tests.test_foobar

If you have init files that will work too. But again, no autocomplete.

Solving this might make working around issue116 easier (the non-import safe
problem)

Google Code Info:
Issue #: 189
Author: kumar.mcmillan
Created On: 2008-05-23T01:05:07.000Z
Closed On:

[dfleury]

I'm having a problem for the same reason.
My team and I are working in a v2 of our project. We decided to leave the legacy apart, but working for while.
To continue using the django test command, we choose to create a new settings file which points to a custom test runner and define a set of arguments that nose should use.

settings_v2.py

TEST_RUNNER = 'runners.V2TestRunner'
NOSE_ARGS = [
    '--where=apps_v2',
]

Folder Hiercharchy Example

- MyProject/
  - my_django_project/
    + foo/
    + bar/
    + baz/
    - apps_v2/
      + new_app_1/
      + new_app_2/
    * settings_v2.py

Running the tests:

$ cd MyProject/my_django_project/
$ ./manage.py test settings=settings_v2

Unfortunately, on line 167 of nose's core.py, if --where is used, the directory will be changed to the one specified by the argument.

core.py@167

        if self.config.workingDir is not None:
            os.chdir(self.config.workingDir)

As a result, a third-party module looks for a folder which should exist at MyProject/my_django_project/, but this is not possible because nose has changed the location to MyProject/my_django_project/apps_v2/.

I tried to comment the lines 167,168 and all worked well. Tests were collected correctly and the working dir preserved. My third-party module is happy now.

I'm not sure if removing this lines is completely safe and I don't get why they exist. However, I think an argument to control this behavior, like --no-path-adjustment, should do.

[dfleury]

Can I make a patch with a --no-chdir argument?