-
Notifications
You must be signed in to change notification settings - Fork 5
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
Multiple run.py
support
#9
Comments
run.py
support lable:enhancement
It's on the roadmap. The idea is if multiple run.py files are found that they are placed at the first level of hierarchy e.g.:
Right now I'm working getting some proper tests in place, bu I think that this would be the next step. |
run.py
support lable:enhancementrun.py
support
Awsome! Can you elaborate on "proper tests" can be a loot of diffrent things, I might be able to help with something :) |
+1 to this issue! |
Hi, I am struggling with the same issue. Any plans / workarounds yet? |
Hi again! :)
I was working with a project with a few submodules with their own
run.py
and noticed that this plugin only handles a single one.Would it be possible to allow wildcard (
*
and**
) patterns in run.py path option and support for multiple run.py.I realize that full regression of the project might not be wanted within this scope.
But not having acces to
Test Explorer: run the rest at current cursor position
&Test Explorer: run tests in current file
steping in to a submodules was quite anoying.The text was updated successfully, but these errors were encountered: