-
Notifications
You must be signed in to change notification settings - Fork 248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question about running tests #208
Comments
There's a hack if you want to test just a module: pyb -P unittest_module_glob=reactor_tests.py whith |
Actually there is: you can override |
Interesting. I usually ended up with my own hack using nosetests:
But this depends on correctly set
|
Hmm.. that would definitely be really easy to add. Question is, what do you gain from it? Right now you I think it would be better to have an actual task that takes parameters, like |
Yeah, I'll do that. Can I get pyb to print the module and scripts path? |
You need to add a task for that :-/ @task
def print_module_path(project):
print(project.expand_path("$dir_source_main_python"))
@task
def print_scripts_path(project):
print(project.expand_path("$dir_source_main_scripts")) and then call the task with |
Yeah, that would suffice for my use-case. Everything, else I can do by shell function. It's probably only an edge-case, since I don't know any projects that override these defaults, but just in case it would be neato and would help interoperability between pybuilder and other tools. |
The original question has been answered. I'd like to close this issue and make a new one for the suggestions about the additional tasks, OK? |
Works for me! |
See: #239 |
Is it possible to run individual tests?
The text was updated successfully, but these errors were encountered: