Provide reason for skipping bignum tests #16

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
2 participants
@paultcochrane

It's good for the user to know why tests are being skipped, hence it's
implemented here. The nicest way to do this was to use the skip_all
option to plan of Test::More, hence Test::More is used instead of
Test. This shouldn't be a problem, since Test::More has been in core
for a long time now.

This PR is submitted in the hope that it is helpful. If it needs to be changed in any way, please just let me know and I'll update it and resubmit.

Provide reason for skipping bignum tests
It's good for the user to know why tests are being skipped, hence it's
implemented here.  The nicest way to do this was to use the `skip_all`
option to `plan` of `Test::More`, hence `Test::More` is used instead of
`Test`.  This shouldn't be a problem, since `Test::More` has been in core
for a long time now.
@toddr

This comment has been minimized.

Show comment
Hide comment
@toddr

toddr Apr 14, 2018

merged to master in toddr@b839602

toddr commented Apr 14, 2018

merged to master in toddr@b839602

@paultcochrane paultcochrane deleted the paultcochrane:pr/explain-bignum-skip branch Apr 14, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment