-
Notifications
You must be signed in to change notification settings - Fork 35
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
Add a way to configure the scope #3
Labels
enhancement
New feature or request
Milestone
Comments
Take a look at I think it does what you want, and is sane. All the existing tests still pass. |
I am waiting for this to be merged in as well :) |
Me too 👍 |
@JoeSc can we create a PR based on your changes? |
+1 |
This will be useful in our case too ! |
I'm all up for this as well! |
Waiting for this as well! Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For the moment, the scope of the dependencies is hard coded to
module
. That means that a test can only be marked as dependent on a test in the same module, but cannot depend on a test in a different module. The backend classDependencyManager
is in principle also capable to work onsession
scope. But the calling hooks do not use the optionalscope
argument in thegetManager()
call.The difficulty is that I have no idea how to define a clean API to configure the scope from the calling tests.
The text was updated successfully, but these errors were encountered: