Using TAP::Parser for system/network monitoring style tests

reisinge has asked for the wisdom of the Perl Monks concerning the following question:

Hello monks,

Inspired by David N. Blank-Edelman (p. 522) I am trying to implement a simple server/network monitoring system based on Test::More. I like the approach of Randal L. Schwartz but he used Test::Harness::Straps which now exists only for backwards compatibility.

How would I use the TAP::Parser for this purpose (lines 34 to 54 of Randal's LISTING TWO)? I found Re^3: Intercepting TAP output. Is there a better way?

Well done is better than well said. -- Benjamin Franklin

Comment on Using TAP::Parser for system/network monitoring style tests

Replies are listed 'Best First'.
Re: Using TAP::Parser for system/network monitoring style tests by daxim (Curate) on Jul 08, 2013 at 16:18 UTC
Test::Server, Test::System	[reply]
Re^2: Using TAP::Parser for system/network monitoring style tests by reisinge (Hermit) on Jul 08, 2013 at 17:45 UTC
After having looked at the documentation I came to these conclusions: Test::Server -- looks good but is missing the TAP parsing part I'm looking for Test::System -- made for different purpose (from its documentation: "One of the things you need to keep in mind is that Test::System is NOT a monitoring system.") Thanks anyway. Well done is better than well said. -- Benjamin Franklin	[reply]
Re^3: Using TAP::Parser for system/network monitoring style tests by MidLifeXis (Monsignor) on Jul 08, 2013 at 17:51 UTC
App::Prove or some other TAP harness would be used to collect the output of a Test::Server-based test suite. The harness (TAP-output-consumer) is separate from the TAP-generating tests themselves (TAP-output-producer). Perhaps I am not quite grokking what you are envisioning. --MidLifeXis	[reply]


Syntactic Confectionery Delight
	PerlMonks