You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not to run the whole suite, but just to run individual files and a directory
Is this a decent way to proceed? PERL5OPT=-MDevel::Cover prove t/MyTest.t t/MyTestDir
It works but there is no output from Devel::Cover so I miss messages like #342
cover -t -make 'prove -Ilib -r t/MyTest.t t/MyTestDir ; exit $?'
Same as the 1st attempt. Works, but silences output of Devel::Cover
prove --exec 'perl -MDevel::Cover -Ilib' t/MyTest.t t/MyTestDir
It works but I have duplicate warnings (e.g. of #342) for each test file. Maybe that's normal?
Here, using a makefile doesn't really fit because it's to review patches and each time I'm running the few relevant test files/directories. To avoid running the whole huge test suite. And it's really great to have a tool as powerful as Devel::Cover to easily check that the new tests are enough to cover the new code :D
So I'm trying to be sure to use the tool right and not cause unintended bad effects.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Not to run the whole suite, but just to run individual files and a directory
Is this a decent way to proceed?
PERL5OPT=-MDevel::Cover prove t/MyTest.t t/MyTestDir
It works but there is no output from Devel::Cover so I miss messages like #342
I found this:
https://stackoverflow.com/questions/11212425/how-to-use-develcover-with-prove
cover -t -make 'prove -Ilib -r t/MyTest.t t/MyTestDir ; exit $?'
Same as the 1st attempt. Works, but silences output of Devel::Cover
prove --exec 'perl -MDevel::Cover -Ilib' t/MyTest.t t/MyTestDir
It works but I have duplicate warnings (e.g. of #342) for each test file. Maybe that's normal?
Here, using a makefile doesn't really fit because it's to review patches and each time I'm running the few relevant test files/directories. To avoid running the whole huge test suite. And it's really great to have a tool as powerful as Devel::Cover to easily check that the new tests are enough to cover the new code :D
So I'm trying to be sure to use the tool right and not cause unintended bad effects.
Beta Was this translation helpful? Give feedback.
All reactions