GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages


Manual Reference Pages  -  TEST2::TOOLS::COMPARE (3)

.ds Aq ’

NAME

Test2::Tools::Compare - Tools for comparing deep data structures.

CONTENTS

DESCRIPTION

Test::More had is_deeply(). This library is the Test2 version. This library can be used to compare data structures. This library goes a step further though, 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.

SYNOPSIS



    use Test2 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/\d+/},
        "a is 1, b is an integer, we dont care about c."
    );



    ADVANCED

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 Compare => *;

    is(
        $some_hash,
        hash {
            field a => 1;
            field b => 2;
            field c => 3;
        },
        "Hash matches spec"
    );



COMPARISON TOOLS

$bool = is($got, $expect)
$bool = is($got, $expect, $name)
$bool = is($got, $expect, $name, @diag) $got is the data structure you want to check. $expect is what you want $got to look like. $name is an optional name for the test. @diag is optional diagnostics messages that will be printed to STDERR in event of failure, they will not be displayed when the comparison is successful. The boolean true/false result of the comparison is returned.

This is the strict checker. The strict checker requires a perfect match between $got and $expect. All hash fields must be specfied, 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/\d+/);    # Note: The match function is not exported by default
            # Dont 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 2 strings:



    is(foo, foo, "strings match");



<B>NoteB>: This is not the tool to use if you want to check if 2 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 cyle and refers back to itself at some point, if this happens an exception will be thrown to break an otherwise infinite recursion.

<B>NoteB>: Non-reference values will be compared as strings using eq, that means ’2.0’ and ’2’ will match.

$bool = isnt($got, $expect)
$bool = isnt($got, $expect, $name)
$bool = isnt($got, $expect, $name, @diag) Opposite of is(). Does all the same checks, but passes when there is a mismatch.
like($got, $expect)
like($got, $expect, $name)
like($got, $expect, $name, @diag) $got is the data structure you want to check. $expect is what you want $got to look like. $name is an optional name for the test. @diag is optional diagnostics messages that will be printed to STDERR in event of failure, they will not be displayed when the comparison is successful. The boolean true/false result of the comparison is returned.

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/\d+/},
        "a is 1, b is an integer, we dont care about other fields"
    );



This works for both deep and shallow structures. For instance you can use this to compare 2 strings:



    like(foo bar, qr/^foo/, "string matches the pattern");



unlike($got, $expect)
unlike($got, $expect, $name)
unlike($got, $expect, $name, @diag) Opposite of like(). Does all the same checks, but passes when there is a mismatch.

    QUICK CHECKS

<B>Note: None of these are exported by default, you need to request them.B>

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);



$check = T() This verifies that the value in the corresponding $got structure is true, any true value will do.



    is($foo, T(), $foo has a true value);

    is(
        { a => xxx },
        { a => T() },
        "The a key is true"
    );



$check = F() This verifies that the value in the corresponding $got structure is false, any false value will do, <B>but the value must existB>.



    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 non-existant 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, as such 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.

$check = D() This is to verify that the value in the $got structure is defined. Any value other than undef will pass.

This will pass:



    is(foo, D(), foo is defined);



This will fail:



    is(undef, D(), foo is defined);



$check = DNE() This can be used to check that no value exists. This is useful to check the end bound of an array, or to check that a key does not exist in a hash.

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");



$check = FDNE() This is a combination of F() and DNE(). This will pass for a false value, or a non-existant value.

    VALUE SPECIFICATIONS

<B>Note: None of these are exported by default, you need to request them.B>
$check = string ‘‘...’’ Verify that the value matches the given string using the eq operator.
$check = number ...; Verify that the value matches the given number using the == operator.
$check = match qr/.../ Verify that the value matches the regex pattern. This form of pattern check will <B>NOTB> stringify references being checked.
$check = mismatch qr/.../ Verify that the value does not match the regex pattern. This form of pattern check will <B>NOTB> stringify references being checked.
$check = validator(sub{ ... })
$check = validator($NAME => sub{ ... })
$check = validator($OP, $NAME, sub{ ... }) The coderef is the only required argument. The coderef should check that the value is what you expect, it should return a boolean true or false. Optionally you can specify a name and operator that are used in diagnostics, they are also provided to the sub itself as named parameters.

Check the value using this sub. The sub gets the value in $_, as well it received 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;
    }



$check = exact_ref($ref) Check that the value is exactly the same reference as the one provided.

    SET BUILDERS

<B>Note: None of these are exported by default, you need to request them.B>
my $check = check_set($check1, $check2, ...) Check that the value matches ALL of the specified checks.
my $check = in_set($check1, $check2, ...) Check that the value matches 1 OR MORE of the specified checks.
not_in_set($check1, $check2, ...) Check that the value DOES NOT match ANY of the specified checks.
check $thing Check that the value matches the specified thing.

    HASH BUILDER

<B>Note: None of these are exported by default, you need to request them.B>



    $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;

        ...

        end(); # optional, enforces that no other keys are present.
    };



$check = hash { ... } This is used to define a hash check.
field $NAME => $VAL
field $NAME => $CHECK Specify a field check. This will check the hash key specified by $NAME and ensure it matches the value in $VAL. You can put any valid check in $VAL, such as the result of another call to array { ... }, DNE(), etc.

<B>Note:B> This function can only be used inside a hash builder sub, and must be called in void context.

end() Enforce that no keys are found in the hash other than those specified. This is essentually the ’use strict’ of a hash check. This can be used anywhere in the hash builder, though typically it is placed at the end.
DNE() This is a handy check that can be used with field() to ensure that a field (D)oes (N)not (E)xist.



    field foo => DNE();



    ARRAY BUILDER

<B>Note: None of these are exported by default, you need to request them.B>



    $check = hash {
        # 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 dont care what it is.
        item 4 => e;

        # Gets index 5.
        item f;

        # Remove any REMAINING items that contain 0-9.
        filter_items { grep {m/\D/} @_ };

        # 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.
    };



$check = array { ... }
item $VAL
item $CHECK
item $IDX, $VAL
item $IDX, $CHECK Add an expected item to the array. If $IDX is not specified it will automatically calculate it based on the last item added. You can skip indexes, which means you do not want them to be checked.

You can provide any value to check in $VAL, or you can provide any valid check object.

<B>Note:B> Items MUST be added in order.

<B>Note:B> This function can only be used inside an array builder sub, and must be called in void context.

filter_items { my @remaining = @_; ...; return @filtered } This function adds a filter, all items remaining in the array from the point the filter is reached will be passed into the filter sub as arguments, the sub should return only the items that should be checked.

<B>Note:B> This function can only be used inside an array builder sub, and must be called in void context.

end() Enforce that there are no indexes after the last one specified. This will not force checking of skipped indexes.
DNE() This is a handy check that can be used with item() to ensure that an index (D)oes (N)not (E)xist.



    item 5 => DNE();



    META BUILDER

<B>Note: None of these are exported by default, you need to request them.B>



    my $check = meta {
        prop blessed => My::Module; # Ensure value is blessed as our package
        prop reftype => HASH;       # Ensure value is a blessed hash
        prop size    => 4;            # Check the number of hash keys
        prop this    => ...;          # Check the item itself
    };



meta { ... } Build a meta check
prop $NAME => $VAL
prop $NAME => $CHECK Check the property specified by $name against the value or check.

Valid properties are:
’blessed’ What package (if any) the thing is blessed as.
’reftype’ Reference type (if any) the thing is.
’this’ The thing itself.
’size’ For array references this returns the number of elements. For hashes this returns the number of keys. For everything else this returns undef.

    OBJECT BUILDER

<B>Note: None of these are exported by default, you need to request them.B>



    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;

        # 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();
    };



$check = object { ... } Specify an object check for use in comparisons.
call $METHOD_NAME => $RESULT
call $METHOD_NAME => $CHECK
call sub { ... }, $RESULT
call sub { ... }, $CHECK Call the specified method (or coderef) and verify the result. The coderef form us useful if you want to check a method that returns a list as it allows you to wrap the result in a reference.



    my $ref = sub {
        my $self = shift;
        my @result = $self->get_list;
        return \@result;
    };

    call $ref => [ ... ];



field $NAME => $VAL Works just like it does for hash checks.
item $VAL
item $IDX, $VAL Works just like it does for array checks.
prop $NAME => $VAL
prop $NAME => $CHECK Check the property specified by $name against the value or check.

Valid properties are:
’blessed’ What package (if any) the thing is blessed as.
’reftype’ Reference type (if any) the thing is.
’this’ The thing itself.
’size’ For array references this returns the number of elements. For hashes this returns the number of keys. For everything else this returns undef.

DNE() Can be used with item, or field to ensure the hash field or array index does not exist. Can also be used with call to ensure a method does not exist.
end() Turn on strict array/hash checking, that is ensure that no extra keys/indexes are present.

    EVENT BUILDERS

<B>Note: None of these are exported by default, you need to request them.B>

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 o
        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
$check = event $TYPE;
$check = event $TYPE => sub { ... };
$check = event $TYPE => { ... }; This works just like an object builder. In addition to supporting everything the object check supports, you also have to specify the event type, and many extra meta-properties are available.

Extra properties are:
’file’ File name to which the event reports (for use in diagnostics).
’line’ Line number to which the event reports (for use in diagnostics).
’package’ Package to which the event reports (for use in diagnostics).
’subname’ Sub that was called to generate the event (example: ok()).
’skip’ Set to the skip value if the result was generated by skipping tests.
’todo’ Set to the todo value if TODO was set when the event was generated.
’trace’ The ’at file foo.t line 42’ string that will be used in diagnostics.
’tid’ Thread id in which the event was generated.
’pid’ PRocess id in which the event was generated.

@checks = fail_events $TYPE;
@checks = fail_events $TYPE => sub { ... };
@checks = fail_events $TYPE => { ... }; Just like event() documented above. The difference is that this produces 2 events, the one you specify, and a Diag after it. There are no extra checks in the Diag.

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.

SOURCE

The source code repository for Test2-Suite can be found at http://github.com/Test-More/Test2-Suite/.

MAINTAINERS

Chad Granum <exodist@cpan.org>

AUTHORS

Chad Granum <exodist@cpan.org>

COPYRIGHT

Copyright 2015 Chad Granum <exodist7@gmail.com>.

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/

Search for    or go to Top of page |  Section 3 |  Main Index


perl v5.20.3 TEST2::TOOLS::COMPARE (3) 2016-03-20

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.