in reply to A way to suppress output of passed tests in a subtest with Test::More?

I'm wondering how I might tame the output so only tests that fail show.

The simplest way I know of is to use prove, as previously discussed.

  • Comment on Re: A way to suppress output of passed tests in a subtest with Test::More?

Replies are listed 'Best First'.
Re^2: A way to suppress output of passed tests in a subtest with Test::More?
by nysus (Parson) on Mar 02, 2017 at 16:45 UTC

    OK, just glanced at the docs. I ran !:prove and it magically worked and tests the files in my /t directory. Nice. I can work with this.

    $PM = "Perl Monk's";
    $MCF = "Most Clueless Friar Abbot Bishop Pontiff Deacon Curate";
    $nysus = $PM . ' ' . $MCF;
    Click here if you love Perl Monks

      From vim:
      !prove -l t/
      Too bad you didn't listen when you were told this months ago. Maybe you will start listening now?
Re^2: A way to suppress output of passed tests in a subtest with Test::More?
by nysus (Parson) on Mar 02, 2017 at 16:41 UTC

    Yes, this prove beast you speak of, I keep seeing it referred to. I avoid it because it keeps talking about this "Tap Harness" stuff which makes me want to hide under my covers. I've got my vim set up running perfectly so I can test my module with the push of a button and now I'm afraid I will have to redo everything to implement prove. Will I have to?

    My current set up is I've got my perl module open in vim and I hit <F7> which triggers a nifty little vim script that searches for and runs all the tests it finds in a directory (vim script written by Damian Conway). The tests output springs open in a new buffer window split to the right of my code and I have it perfectly syntax highlighted to my liking.

    Am I going to have to undo my perfect little set up in order to use prove?

    $PM = "Perl Monk's";
    $MCF = "Most Clueless Friar Abbot Bishop Pontiff Deacon Curate";
    $nysus = $PM . ' ' . $MCF;
    Click here if you love Perl Monks