Re^4: swat on CPAN

That is exactly what swat does - it calls prove with parameters: swat directory host prove-parameters Like for your example: swat directory host --formatter TAP::Formatter::JUnit

If no prove parameters are given swat just call prove as is and then we have tap output.

Sorry, did not understand your idea about plack/psgi , could you please explain ?

Comment on Re^4: swat on CPAN Select or Download Code

Replies are listed 'Best First'.
Re^5: swat on CPAN by Anonymous Monk on Jul 17, 2015 at 19:16 UTC
So how does one disable `--formatter TAP::Formatter::JUnit`? Would you provide a usage example that shows this being disabled?	[reply]
Re^6: swat on CPAN by melezhik (Monk) on Jul 17, 2015 at 19:38 UTC
Why one need to disable this? One may choose b/w different formats - TAP, JUnit, whatever supported by prove and it's plugins . You may find one matching your needs. Did I answer , or I miss something. Please be specific . Thanks	[reply]
Re^7: swat on CPAN by Anonymous Monk on Jul 17, 2015 at 19:45 UTC
Just pointing out one of the many fundamental flaws in your solution. You do not wrap `prove` on behalf of the client. You instead produce test files and let the client choose the driver that runs the tests through the harness. "Why one need to disable this?" Again, the best CPAN modules allow the client to configure what they want.	[reply]
Re^8: swat on CPAN by melezhik (Monk) on Jul 17, 2015 at 19:50 UTC
Re^9: swat on CPAN by Anonymous Monk on Jul 17, 2015 at 19:52 UTC
Some notes below your chosen depth have not been shown here