Tagging tests

Is there any way to 'tag' tests in Perl? What I mean is, that ideally, if you tagged all your tests according to the functionality they depended on, you could use the tags to more easily work out what was going wrong. # Looks like you failed 21 tests of 75. # Failures by tag: # syntax: 0/50 # l

Re: Tagging tests

Thanks, I'll look into both! Daniel On 1 May 2012 19:17, Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 wrote: >> Is there any way to 'tag' tests in Perl? > > >> - If there are common problems (computer can't access the net, unicode >> handling is dodgy), this makes it more straightforward to dia

Re: Proposal Test::TAPv13

I may have missed the point here, but would it be sufficient to have two flavours of diagnostic calls, distinguishing between pre-test diagnostics (`forewarn()`) and post-test diagnostics (`reflect()`), or is the problem that ok() must be a single function call? If that's possible, maybe we can ex

Re: [LDTP-Dev] Announce: Cobra 2.0 - Windows GUI test automation tool

QBasic? On 03/08/2012, Gabor Szabo wrote: > FYI something is really missing there :-( > Gabor > > -- Forwarded message -- > From: Nagappan Alagappan > > * Java / C# / VB.NET / PowerShell / Ruby are now officially supported > LDTP scripting languages other than Python > > [...]

Re: Running perl from a test on Windows

"I need to collect the output from the other Perl library *without loading it*, because I also want to make sure that my library loads it for me" Is there a reason the output has to be created during testing rather than being part of the distribution? What about running it out in a .t file which pr