Groups | Search | Server Info | Login | Register
| Newsgroups | perl.qa |
|---|---|
| Date | 2016-12-18 09:08 -0500 |
| Subject | Test-Deep as_test_deep_cmp branch |
| Message-ID | <20161218140823.GA8199@debian> (permalink) |
| From | perl.qa@rjbs.manxome.org (Ricardo Signes) |
[Multipart message — attachments visible in raw view] - view raw
I've filed a PR against Test-Deep: https://github.com/rjbs/Test-Deep/pull/52 addresses https://github.com/rjbs/Test-Deep/issues/50 The idea is: When you call cmp_deeply($have, $want), objects found in $want are either Test::Deep::Cmp objects or not. If they are, they do their special test magic. If they are not, they are more or less compared to the data in $have without respect to blessing. For example, a blessed hashref in $want is compared to the matching data in $have for keys and values. With my changes, objects in $want are checked for a as_test_deep_cmp method, which can be called to return a Test::Deep::Cmp to be used instead of the object. I expect this to be rarely, but sometimes, useful. Issue #50 goes into the details of why it came up. In that, I mention using this with JSON::Typist/Test::Deep::JType. I have implemented the described feature at https://github.com/rjbs/JSON-Typist/pull/2 I'm interested in any thoughts on this before I make a trial release. -- rjbs
Back to perl.qa | Previous | Next — Next in thread | Find similar
Test-Deep as_test_deep_cmp branch perl.qa@rjbs.manxome.org (Ricardo Signes) - 2016-12-18 09:08 -0500 Re: Test-Deep as_test_deep_cmp branch perl.qa@rjbs.manxome.org (Ricardo Signes) - 2016-12-27 08:50 -0500
csiph-web