Ovid <publiustemp-perl...@yahoo.com> writes:
> it's getting harder to find out which TODO tests are unexpectedly
> passing.
> [...]
> Suggestions?
I am spoiling my own YAPC::EU 2009 talk here but try this toolchain:
# the tool chain
$ cpan App::DPath
# prepare example project which contains passing TODOs
$ cd /tmp/
$ git clone g...@github.com:renormalist/data-dpath.git
$ cd data-dpath
# the query on TAP
$ perl -Ilib xt/alltest.t 2>&1 | \
dpath -i tap '//has_todo[value==1]/../is_actual_ok[value == 1]/..'
---
-
as_string: "ok 149 - ANYWHERE + NOSTEP + FILTER int (REFERENCES) # TODO
deferred"
description: "- ANYWHERE + NOSTEP + FILTER int (REFERENCES)"
directive: TODO
explanation: deferred
has_skip: 0
has_todo: 1
is_actual_ok: 1
is_bailout: 0
is_comment: 0
is_ok: 1
is_plan: 0
is_pragma: 0
is_test: 1
is_unknown: 0
is_unplanned: 0
is_version: 0
is_yaml: 0
number: 149
raw: "ok 149 - ANYWHERE + NOSTEP + FILTER int (REFERENCES) # TODO deferred"
type: test
Not sure it fits to your aggregated monster TAP yet, it has known
size&speed limits.
Kind regards,
Steffen
--
Steffen Schwigon <s...@renormalist.net>
Dresden Perl Mongers <http://dresden-pm.org/>
Deutscher Perl-Workshop <http://www.perl-workshop.de/>
