jeffh
running sniffer over multiple directories ...
is this actually an issue? More like a feature request - would be nice to have sniffer descend all sub-directories ...?
Wouldn't it be the same to start sniffer in the parent directory then? or am I missing some context here?
I have a directory structure like this:
folder1 contains folder2
folder1 contains some tests, as does folder2
Currently the only way to run the tests in folder2 is to start sniffer in that directory, i.e. if I run sniffer in folder1 it does not seem to find the tests in the subfolder.
It's not a critical issue right now, but it would be nice to be able to tell sniffer to search all sub-directories for tests - perhaps there is some setting to achieve this that I am missing?
Apologies in advance if I am again missing something obvious ...
I needed the same kind of functionality, wrote a scent.py file that tried to make it work, but ended up throwing it away and building something from scratch with watchdog instead.
http://serialized.net/2012/09/local-python-ci-with-watchdog-and-nose/
The biggest functionality problem with sniffer seemed to be that I couldn't get the name of the file that was modified in the test running phase, which I needed. (When you've got 6 packages, you really want to test the one you're editing first, because odds are it's the one you just broke, and you don't want to wait to find that out.)
As far as I understand the code (see scent_picker.py), it is possible to use more directories that the current one using
watch_paths = ['.', 'examples']
Does this solve your problem?
