-
Notifications
You must be signed in to change notification settings - Fork 32
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
Please make _run_test_class and _run_test_method public #88
Comments
Seems like a good idea. We should probably also have a public |
I also realized that for this to really function properly you need a way to pass roles to be applied to the executor into the runner class. Right now it hard codes the Sequential & Executor class names, so there's no way to tell it to use a subclass. Allowing arbitrary roles to be applied to the executor would make it easier for folks to write plugins. |
This is done in v0.92. |
It's trivial to override the executor in
Test::Class::Moose::Runner
to make a custom subclass, but when subclassingTest::Class::Moose::Executor::Sequential
, I have to use the private methods_run_test_class
and_run_test_method
with mybefore
modifiers.It would be lovely if those were made public so I didn't feel too guilty about those. If those were public, I could easily publish modules which allow verbose output like the following (without needing to extend functionality with PRs such as #76):
The text was updated successfully, but these errors were encountered: