peczenyj / GDPR-IAB-TCFv2 / 25463473810
96%
main: 96%

LAST BUILD BRANCH: devel
DEFAULT BRANCH: main
Ran
Jobs 1
Files 11
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 95.63%. Remained the same
25463473810

push

github

web-flow 
test: assert CLI dump JSON structurally instead of by regex (#56)

The CPAN Testers report 4f448578-4978-11f1-9737-f43e6e8775ea
(x86_64-linux-thread-multi, Perl 5.32.1, Amazon Linux 2) flagged
'CLI isolated vendor consents' in t/09-predicates.t as failing.

The assertion was a regex over the encoded JSON output:

    like( $out, qr/"vendor":\{.*"consents":\{"1":true\}/s, ... );

That implicitly required the encoder to emit `vendor` before any
other top-level key carrying a `consents` block, AND vendor 1 to be
the first key inside `vendor.consents`.  Both depend on hash-key
order, which is non-deterministic across Perl versions, JSON
encoders (JSON::XS vs JSON::PP), and hash randomization.

Replace each regex-on-JSON assertion in the `CLI --vendor-id option`
subtest with a structural check after decoding the output:

  - is_deeply on `[ keys vendor.consents ]` to assert isolation
  - ok( $data->{vendor}{consents}{1} ) for the boolean value
  - !exists $data->{vendor}{disclosed}{23} for the negative case
  - is_deeply between the long- and short-form invocations to assert
    -v matches --vendor-id

The companion `unlike(qr/^iabtcfv2 version/, ...)` line stays as a
regex, since it's checking plain text output, not JSON.

JSON loading mirrors the pattern in t/10-cli-iabtcfv2.t: try JSON,
fall back to JSON::PP, plan skip_all if neither is available.

744 of 778 relevant lines covered (95.63%)

11588.29 hits per line

Jobs
ID Job ID Ran Files Coverage
1 25463473810.1 11
95.63
 GitHub Action Run
Source Files on build 25463473810