-
Notifications
You must be signed in to change notification settings - Fork 9
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
Stop requireing Devel::Cover #17
Comments
+1
This is already the case. The only part missing is this being changed to "recommends" or somesuch. Currently Devel::Cover does not build on blead, and as such drags this module with it. |
To work around pjcj/Devel--Cover#161 provide a fake Devel::Cover satisfying manwar/Test-Strict#17
Hi @ribasushi, I will sort this out by end of play today. Best Regards, |
The current solution is suboptimal. While it does solve my problem of reducing the dependency footrpint, it would not alert an end-user who requested You should consider failing the test when |
This seems to have been resolved, @szabgab I'd close |
Closing the issue as confirmed above. |
I think most of the people who use Test::Critic don't need the functionality provided by Devel::Cover. IMHO Test::Strict should not depend on it and if the user invokes the
all_cover_ok
then it should be checked if Devel::Cover is installed.The text was updated successfully, but these errors were encountered: