Re: GUI Interface to Test::* scripts

If I were to do this, I would start with a Tk or other GUI app that launches tests from with IPC::Run or IPC::Open3 or something and uses Test::Harness::Straps to parse the results into data structures.

If it's easy to use and configure, I'd try it.

Comment on Re: GUI Interface to Test::* scripts

Replies are listed 'Best First'.
Re^2: GUI Interface to Test::* scripts by ChrisS (Monk) on Jun 09, 2005 at 16:08 UTC
Thanks for the Test::Harness::Straps tip. Is there a particular advantage to using IPC::Run or IPC::Open3 over a straight call to the `analyze_file` method from Test::Harness::Straps? Would using one of them allow for capturing the `STDERR` output for test failures?	[reply] [d/l] [select]
Re^3: GUI Interface to Test::* scripts by chromatic (Archbishop) on Jun 09, 2005 at 17:33 UTC
Yes, that's exactly the advantage I had in mind, especially if you use a new enough version of Test::Harness::Straps that can parse diagnostic output.	[reply]