Test2::Tools::Compare(3) | Perl Programmers Reference Guide | Test2::Tools::Compare(3) |
Test2::Tools::Compare - Tools for comparing deep data structures.
Test::More had is_deeply(). This library is the Test2 version that can be used to compare data structures, but goes a step further in that it provides tools for building a data structure specification against which you can verify your data. There are both 'strict' and 'relaxed' versions of the tools.
use Test2::Tools::Compare; # Hash for demonstration purposes my $some_hash = {a => 1, b => 2, c => 3}; # Strict checking, everything must match is( $some_hash, {a => 1, b => 2, c => 3}, "The hash we got matches our expectations" ); # Relaxed Checking, only fields we care about are checked, and we can use a # regex to approximate a field. like( $some_hash, {a => 1, b => qr/\A[0-9]+\z/}, "'a' is 1, 'b' is an integer, we don't care about 'c'." );
Declarative hash, array, and objects builders are available that allow you to generate specifications. These are more verbose than simply providing a hash, but have the advantage that every component you specify has a line number associated. This is helpful for debugging as the failure output will tell you not only which fields was incorrect, but also the line on which you declared the field.
use Test2::Tools::Compare qw{ is like isnt unlike match mismatch validator hash array bag object meta number float rounded within string subset bool in_set not_in_set check_set item field call call_list call_hash prop check all_items all_keys all_vals all_values etc end filter_items T F D DF E DNE FDNE U L event fail_events exact_ref }; is( $some_hash, hash { field a => 1; field b => 2; field c => 3; }, "Hash matches spec" );
This is the strict checker. The strict checker requires a perfect match between $got and $expect. All hash fields must be specified, all array items must be present, etc. All non-scalar/hash/array/regex references must be identical (same memory address). Scalar, hash and array references will be traversed and compared. Regex references will be compared to see if they have the same pattern.
is( $some_hash, {a => 1, b => 2, c => 3}, "The hash we got matches our expectations" );
The only exception to strictness is when it is given an $expect object that was built from a specification, in which case the specification determines the strictness. Strictness only applies to literal values/references that are provided and converted to a specification for you.
is( $some_hash, hash { # Note: the hash function is not exported by default field a => 1; field b => match(qr/\A[0-9]+\z/); # Note: The match function is not exported by default # Don't care about other fields. }, "The hash comparison is not strict" );
This works for both deep and shallow structures. For instance you can use this to compare two strings:
is('foo', 'foo', "strings match");
Note: This is not the tool to use if you want to check if two references are the same exact reference, use ref_is() from the Test2::Tools::Ref plugin instead. Most of the time this will work as well, however there are problems if your reference contains a cycle and refers back to itself at some point. If this happens, an exception will be thrown to break an otherwise infinite recursion.
Note: Non-reference values will be compared as strings using "eq", so that means strings '2.0' and '2' will not match, but numeric 2.0 and 2 will, since they are both stringified to '2'.
This is the relaxed checker. This will ignore hash keys or array indexes that you do not actually specify in your $expect structure. In addition regex and sub references will be used as validators. If you provide a regex using "qr/.../", the regex itself will be used to validate the corresponding value in the $got structure. The same is true for coderefs, the value is passed in as the first argument (and in $_) and the sub should return a boolean value. In this tool regexes will stringify the thing they are checking.
like( $some_hash, {a => 1, b => qr/\A[0-9]+\z/}, "'a' is 1, 'b' is an integer, we don't care about other fields" );
This works for both deep and shallow structures. For instance you can use this to compare two strings:
like('foo bar', qr/^foo/, "string matches the pattern");
The is(), isnt(), like(), and unlike() functions can be made to dump $got using Data::Dumper when tests fail by setting the "T2_AUTO_DUMP" environment variable to "1". (Alternatively, "T2_AUTO_DUMP" can be set to the name of a Perl module providing a compatible Dump() method.) The "T2_AUTO_DEPARSE" environment variable can be used to enable Data::Dumper's deparsing of coderefs.
Note: None of these are exported by default. You need to request them.
Quick checks are a way to quickly generate a common value specification. These can be used in structures passed into "is" and "like" through the $expect argument.
Example:
is($foo, T(), '$foo has a true value');
is($foo, T(), '$foo has a true value'); is( { a => 'xxx' }, { a => T() }, "The 'a' key is true" );
is($foo, F(), '$foo has a false value'); is( { a => 0 }, { a => F() }, "The 'a' key is false" );
It is important to note that a nonexistent value does not count as false. This check will generate a failing test result:
is( { a => 1 }, { a => 1, b => F() }, "The 'b' key is false" );
This will produce the following output:
not ok 1 - The b key is false # Failed test "The 'b' key is false" # at some_file.t line 10. # +------+------------------+-------+---------+ # | PATH | GOT | OP | CHECK | # +------+------------------+-------+---------+ # | {b} | <DOES NOT EXIST> | FALSE | FALSE() | # +------+------------------+-------+---------+
In Perl, you can have behavior that is different for a missing key vs. a false key, so it was decided not to count a completely absent value as false. See the DNE() shortcut below for checking that a field is missing.
If you want to check for false and/or DNE use the FDNE() check.
This will pass:
is('foo', D(), 'foo is defined');
This will fail:
is(undef, D(), 'foo is defined');
This will pass:
is(undef, U(), 'not defined');
This will fail:
is('foo', U(), 'not defined');
This will pass:
is(0, DF(), 'foo is defined but false');
These will fail:
is(undef, DF(), 'foo is defined but false'); is(1, DF(), 'foo is defined but false');
These pass:
is(['a', 'b', undef], ['a', 'b', E()], "There is a third item in the array"); is({a => 1, b => 2}, {a => 1, b => E()}, "The 'b' key exists in the hash");
These will fail:
is(['a', 'b'], ['a', 'b', E()], "Third item exists"); is({a => 1}, {a => 1, b => E()}, "'b' key exists");
These pass:
is(['a', 'b'], ['a', 'b', DNE()], "There is no third item in the array"); is({a => 1}, {a => 1, b => DNE()}, "The 'b' key does not exist in the hash");
These will fail:
is(['a', 'b', 'c'], ['a', 'b', DNE()], "No third item"); is({a => 1, b => 2}, {a => 1, b => DNE()}, "No 'b' key");
These will pass:
is('foo', L(), 'value is defined and has length'); is([], L(), 'value is defined and has length');
These will fail:
is(undef, L(), 'value is defined and has length'); is('', L(), 'value is defined and has length');
Note: None of these are exported by default. You need to request them.
If a 'precision' parameter is specified, both operands will be rounded to 'precision' number of fractional decimal digits and compared with "eq".
is($near_val, float($val, precision => 4), "Near 4 decimal digits");
Otherwise, the check will be made within a range of +/- 'tolerance', with a default 'tolerance' of 1e-08.
is( $near_val, float($val, tolerance => 0.01), "Almost there...");
See also "within" and "rounded".
If a 'precision' parameter is specified, both operands will be rounded to 'precision' number of fractional decimal digits and compared with "eq".
Otherwise, the check will be made within a range of +/- 'tolerance', with a default 'tolerance' of 1e-08.
See also "!within" and "!rounded".
$tolerance is optional and defaults to 1e-08.
$tolerance is optional and defaults to 1e-08.
Note: "!mismatch()" is documented for completion, please do not use it.
Note: mismatch() was created before overloading of "!" for match() was a thing.
Check the value using this sub. The sub gets the value in $_, and it receives the value and several other items as named parameters.
my $check = validator(sub { my %params = @_; # These both work: my $got = $_; my $got = $params{got}; # Check if a value exists at all my $exists = $params{exists} # What $OP (if any) did we specify when creating the validator my $operator = $params{operator}; # What name (if any) did we specify when creating the validator my $name = $params{name}; ... return $bool; }
Note: None of these are exported by default. You need to request them.
Note: None of these are exported by default. You need to request them.
$check = hash { field foo => 1; field bar => 2; # Ensure the 'baz' keys does not even exist in the hash. field baz => DNE(); # Ensure the key exists, but is set to undef field bat => undef; # Any check can be used field boo => $check; # Set checks that apply to all keys or values. Can be done multiple # times, and each call can define multiple checks, all will be run. all_vals match qr/a/, match qr/b/; # All values must have an 'a' and a 'b' all_keys match qr/x/; # All keys must have an 'x' ... end(); # optional, enforces that no other keys are present. };
Note: This function can only be used inside a hash builder sub, and must be called in void context.
field foo => DNE();
Note: None of these are exported by default. You need to request them.
$check = array { # Uses the next index, in this case index 0; item 'a'; # Gets index 1 automatically item 'b'; # Specify the index item 2 => 'c'; # We skipped index 3, which means we don't care what it is. item 4 => 'e'; # Gets index 5. item 'f'; # Remove any REMAINING items that contain 0-9. filter_items { grep {!m/[0-9]/} @_ }; # Set checks that apply to all items. Can be done multiple times, and # each call can define multiple checks, all will be run. all_items match qr/a/, match qr/b/; all_items match qr/x/; # Of the remaining items (after the filter is applied) the next one # (which is now index 6) should be 'g'. item 6 => 'g'; item 7 => DNE; # Ensure index 7 does not exist. end(); # Ensure no other indexes exist. };
You can provide any value to check in $VAL, or you can provide any valid check object.
Note: Items MUST be added in order.
Note: This function can only be used inside an array, bag or subset builder sub, and must be called in void context.
Note: This function can only be used inside an array builder sub, and must be called in void context.
item 5 => DNE();
Note: None of these are exported by default. You need to request them.
$check = bag { item 'a'; item 'b'; end(); # Ensure no other elements exist. };
A bag is like an array, but we don't care about the order of the items. In the example, $check would match both "['a','b']" and "['b','a']".
You can provide any value to check in $VAL, or you can provide any valid check object.
Note: This function can only be used inside an array, bag or subset builder sub, and must be called in void context.
Note: None of these are exported by default. You need to request them.
$check = subset { item 'a'; item 'b'; item 'c'; # Doesn't matter if the array has 'd', the check will skip past any # unknown items until it finds the next one in our subset. item 'e'; item 'f'; };
You can provide any value to check in $VAL, or you can provide any valid check object.
Note: Items MUST be added in order.
Note: This function can only be used inside an array, bag or subset builder sub, and must be called in void context.
Note: None of these are exported by default. You need to request them.
my $check = meta { prop blessed => 'My::Module'; # Ensure value is blessed as our package prop reftype => 'HASH'; # Ensure value is a blessed hash prop isa => 'My::Base'; # Ensure value is an instance of our class prop size => 4; # Check the number of hash keys prop this => ...; # Check the item itself };
Valid properties are:
Note: None of these are exported by default. You need to request them.
my $check = object { call foo => 1; # Call the 'foo' method, check the result. # Call the specified sub-ref as a method on the object, check the # result. This is useful for wrapping methods that return multiple # values. call sub { [ shift->get_list ] } => [...]; # This can be used to ensure a method does not exist. call nope => DNE(); # Check the hash key 'foo' of the underlying reference, this only works # on blessed hashes. field foo => 1; # Check the value of index 4 on the underlying reference, this only # works on blessed arrays. item 4 => 'foo'; # Check the meta-property 'blessed' of the object. prop blessed => 'My::Module'; # Check if the object is an instance of the specified class. prop isa => 'My::Base'; # Ensure only the specified hash keys or array indexes are present in # the underlying hash. Has no effect on meta-property checks or method # checks. end(); };
The coderef form is useful if you need to do something more complex.
my $ref = sub { local $SOME::GLOBAL::THING = 3; return [shift->get_values_for('thing')]; }; call $ref => ...;
call_list get_items => [ ... ];
call_hash get_items => { ... };
Valid properties are:
Note: None of these are exported by default. You need to request them.
Check that we got an event of a specified type:
my $check = event 'Ok';
Check for details about the event:
my $check = event Ok => sub { # Check for a failure call pass => 0; # Effective pass after TODO/SKIP are accounted for. call effective_pass => 1; # Check the diagnostics call diag => [ match qr/Failed test foo/ ]; # Check the file the event reports to prop file => 'foo.t'; # Check the line number the event reports to prop line => '42'; # You can check the todo/skip values as well: prop skip => 'broken'; prop todo => 'fixme'; # Thread-id and process-id where event was generated prop tid => 123; prop pid => 123; };
You can also provide a fully qualified event package with the '+' prefix:
my $check = event '+My::Event' => sub { ... }
You can also provide a hashref instead of a sub to directly check hash values of the event:
my $check = event Ok => { pass => 1, ... };
USE IN OTHER BUILDERS
You can use these all in other builders, simply use them in void context to have their value(s) appended to the build.
my $check = array { event Ok => { ... }; event Note => { ... }; fail_events Ok => { pass => 0 }; # Get a Diag for free. };
SPECIFICS
Extra properties are:
NOTE: Event checks have an implicit etc() added. This means you need to use end() if you want to fail on unexpected hash keys or array indexes. This implicit etc() extends to all forms, including builder, hashref, and no argument.
Use this to validate a simple failure where you do not want to be bothered with the default diagnostics. It only adds a single Diag check, so if your failure has custom diagnostics you will need to add checks for them.
The source code repository for Test2-Suite can be found at https://github.com/Test-More/Test2-Suite/.
Copyright 2018 Chad Granum <exodist@cpan.org>.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
See http://dev.perl.org/licenses/
2024-04-28 | perl v5.40.0 |