Less verbose printer

[robsontenorio]

It would be nice to have a less verbose option. Just that "dots", but keep the "beauty error handler".

[nunomaduro]

Ideas on this?

[robsontenorio]

Just for clarifying.

Allow to use this output, but keep the collision error hanlder.

[nunomaduro]

I think we do better than that.

[robsontenorio]

Sometimes you just want a overview of tests (with "dots" report), but also a nice error handler output.

Once collision is a "printer" i really don't know if it would be possible to configure through params. But if so, i am willing to submit a PR.

[nunomaduro]

@AlexMartinFR is working on that.

[zembrowski]

@mikeerickson does a great job with phpunit-pretty-result-printer. The output is very minimalistic.

The only thing missing there is an integration with Collision. It would be a perfect match to get phpunit-pretty-result-printer with your collision error handler, Nuno.

Any chances to get back the Listener which was removed in v4.1?

[jaggy]

Hi there! I just wanted to show interest in this issue as well.

Using php artisan test seems to be a bit slower (35s) than using phpunit's default printer (16s). I'm not sure if it's related with the printer but it's the only connecting thread I see.

[mikeerickson]

@zembrowski @jaggy @robsontenorio keep your eyes pealed for an upcoming release of printer which will have something similar to previous listener integrated with phpunit-pretty-result-printer

[mikeerickson]

@AlexMartinFR Is this something that is still on your radar, or have you ditched the plans? If this is still no your radar, that would be fantastic.

[nunomaduro]

@mikeerickson I will probably tackle this myself before PEST v1, and before Laravel 9.

[AlexMartinFR]

Great new Nuno 👍

I've hit roadblocks when I tried to implement it properly, and haven't had a chance to try again yet.
Would it help if I shared what I tried and what I was stuck on?

[mikeerickson]

@nunomaduro was this implemented or did you decide to drop it?