Start 2009-12-31T04:05:07 ActivePerl-818 CPAN-1.9402 Going to read '/home/fly818/var/cpan/Metadata' Database was generated on Thu, 31 Dec 2009 21:50:21 GMT Running make for M/MA/MARKSTOS/Data-FormValidator-4.65.tar.gz Checksum for /net/nas/data/cpan/authors/id/M/MA/MARKSTOS/Data-FormValidator-4.65.tar.gz ok Will not use Archive::Tar, need 1.00 Data-FormValidator-4.65 Data-FormValidator-4.65/MANIFEST Data-FormValidator-4.65/RELEASE_NOTES Data-FormValidator-4.65/META.yml Data-FormValidator-4.65/Build.PL Data-FormValidator-4.65/Changes Data-FormValidator-4.65/README Data-FormValidator-4.65/MANIFEST.SKIP Data-FormValidator-4.65/test Data-FormValidator-4.65/test/00_base.profile Data-FormValidator-4.65/test/00_base.badformat Data-FormValidator-4.65/lib Data-FormValidator-4.65/lib/Data Data-FormValidator-4.65/lib/Data/FormValidator.pm Data-FormValidator-4.65/lib/Data/FormValidator Data-FormValidator-4.65/lib/Data/FormValidator/Filters.pm Data-FormValidator-4.65/lib/Data/FormValidator/ConstraintsFactory.pm Data-FormValidator-4.65/lib/Data/FormValidator/Results.pm Data-FormValidator-4.65/lib/Data/FormValidator/Constraints.pm Data-FormValidator-4.65/lib/Data/FormValidator/Constraints Data-FormValidator-4.65/lib/Data/FormValidator/Constraints/Dates.pm Data-FormValidator-4.65/lib/Data/FormValidator/Constraints/Upload.pm Data-FormValidator-4.65/t Data-FormValidator-4.65/t/dates.t Data-FormValidator-4.65/t/28_defaults_for_new.t Data-FormValidator-4.65/t/dates_closure.t Data-FormValidator-4.65/t/20_careful_exception_handling.t Data-FormValidator-4.65/t/04_arrayify_undef.t Data-FormValidator-4.65/t/upload_post_text.txt Data-FormValidator-4.65/t/filter_constraints.t Data-FormValidator-4.65/t/26_qr.t Data-FormValidator-4.65/t/dependency_coderef.t Data-FormValidator-4.65/t/credit_card.t Data-FormValidator-4.65/t/ValidatorPackagesTest1.pm Data-FormValidator-4.65/t/results_success.t Data-FormValidator-4.65/t/pod.t Data-FormValidator-4.65/t/11_procedural_match.t Data-FormValidator-4.65/t/21_multiple_fields.t Data-FormValidator-4.65/t/06_regexp_map.t Data-FormValidator-4.65/t/ValidatorPackagesTest2.pm Data-FormValidator-4.65/t/constraints_builtin_closure.t Data-FormValidator-4.65/t/constraint_regexp_map_profile_reuse.t Data-FormValidator-4.65/t/constraints_reuse.t Data-FormValidator-4.65/t/tt_and_overload.t Data-FormValidator-4.65/t/regexp_common_closure.t Data-FormValidator-4.65/t/constraints_regexp_map_interaction.t Data-FormValidator-4.65/t/dependency_groups.t Data-FormValidator-4.65/t/19_refs_as_values.t Data-FormValidator-4.65/t/get_filtered_data.t Data-FormValidator-4.65/t/15_literal_param_constraints.t Data-FormValidator-4.65/t/18_constraint_refs.t Data-FormValidator-4.65/t/05_valid_ip_address.t Data-FormValidator-4.65/t/13_validator_packages.t Data-FormValidator-4.65/t/27_qualify_ref_happy_death.t Data-FormValidator-4.65/t/16_cgi_object.t Data-FormValidator-4.65/t/any_errors.t Data-FormValidator-4.65/t/profile_checking.t Data-FormValidator-4.65/t/upload_closure.t Data-FormValidator-4.65/t/FV_length.t Data-FormValidator-4.65/t/check_profile_syntax.t Data-FormValidator-4.65/t/30_filter_definedness.t Data-FormValidator-4.65/t/constraints_factory.t Data-FormValidator-4.65/t/undefined_arrayref.t Data-FormValidator-4.65/t/params_not_mentioned.t Data-FormValidator-4.65/t/untaint.pl Data-FormValidator-4.65/t/upload.t Data-FormValidator-4.65/t/constraint_method_string.t Data-FormValidator-4.65/t/procedural_valid.t Data-FormValidator-4.65/t/missing_optional.t Data-FormValidator-4.65/t/upload_mime_types.t Data-FormValidator-4.65/t/03_dependency.t Data-FormValidator-4.65/t/msgs.t Data-FormValidator-4.65/t/17_multi_valued_keys.t Data-FormValidator-4.65/t/09_require_some.t Data-FormValidator-4.65/t/get_input_data.t Data-FormValidator-4.65/t/unknown.t Data-FormValidator-4.65/t/filters_builtin.t Data-FormValidator-4.65/t/00_base.t Data-FormValidator-4.65/t/constraints_builtin.t Data-FormValidator-4.65/t/25_results.t Data-FormValidator-4.65/t/02_code_ref.t Data-FormValidator-4.65/t/regexp_common.t Data-FormValidator-4.65/t/constraint_method.t Data-FormValidator-4.65/t/multiple_constraints.t Data-FormValidator-4.65/t/simple.t Data-FormValidator-4.65/t/untaint.t Data-FormValidator-4.65/t/filters_shouldnt_modify.t Data-FormValidator-4.65/t/constraint_method_zero.t Data-FormValidator-4.65/t/constraints_invalid_once_only.t CPAN.pm: Going to build M/MA/MARKSTOS/Data-FormValidator-4.65.tar.gz >>> /home/fly818/ap818/bin/perl-static Build.PL Creating new 'MYMETA.yml' with configuration results Creating new 'Build' script for 'Data-FormValidator' version '4.65' >>> ./Build ./Build: blib/lib/Data/FormValidator/Constraints/Upload.pm: cannot resolve L in paragraph 111. ./Build: blib/lib/Data/FormValidator/Constraints/Upload.pm: cannot resolve L in paragraph 111. ./Build: blib/lib/Data/FormValidator/Constraints/Upload.pm: cannot resolve L in paragraph 111. Building Data-FormValidator MARKSTOS/Data-FormValidator-4.65.tar.gz ./Build -- OK Running Build test >>> ./Build test verbose=1 t/00_base.t .............................. 1..5 ok 1 - use Data::FormValidator; ok 2 - second argument must be a hash ref or die ok 3 - bad profile file names should cause death ok 4 - profile files should return a hash ref ok 5 - loading a profile from a file works ok t/02_code_ref.t .......................... 1..8 ok 1 ok 2 ok 3 ok 4 ok 5 ok 6 ok 7 ok 8 ok t/03_dependency.t ........................ 1..23 ok 1 - no eval problems ok 2 - missing cc_num ok 3 - missing cc_exp ok 4 - missing cc_name ok 5 - no eval problems ok 6 - returned object isa Data::FormValidator::Results ok 7 - has_missing returned true ok 8 - missing('cc_num') returned true ok 9 - missing('cc_exp') returned true ok 10 - missing('cc_name') returned true ok 11 - no eval problems ok 12 - missing cc_num ok 13 - not missing cc_exp ok 14 - not missing cc_name ok 15 - no eval problems ok 16 - returned object isa Data::FormValidator::Results ok 17 - has_missing returned true ok 18 - missing('cc_num') returned true ok 19 - missing('cc_exp') returned false ok 20 - missing('cc_name') returned false ok 21 - using CGI.pm object for input ok 22 - missing('cc_exp') returned false ok 23 - missing('cc_name') returned false ok t/04_arrayify_undef.t .................... 1..4 ok 1 - checks for correct behavior when 'required' # is not specified; fails if _arrayify() does not return an empty list ok 2 - checks for correct behavior when 'required' # is not specified; fails if _arrayify() does not return an empty list ok 3 - arrayref with first element undef... in scalar context ok 4 - arrayref with first element undef..in list context ok t/05_valid_ip_address.t .................. 1..2 ok 1 ok 2 ok t/06_regexp_map.t ........................ 1..5 ok 1 ok 2 ok 3 ok 4 ok 5 ok t/09_require_some.t ...................... 1..4 ok 1 ok 2 ok 3 ok 4 ok t/11_procedural_match.t .................. 1..26 ok 1 ok 2 ok 3 ok 4 ok 5 ok 6 ok 7 ok 8 ok 9 ok 10 ok 11 ok 12 ok 13 ok 14 ok 15 ok 16 ok 17 ok 18 ok 19 ok 20 ok 21 ok 22 ok 23 ok 24 ok 25 ok 26 ok t/13_validator_packages.t ................ 1..8 ok 1 ok 2 ok 3 ok 4 ok 5 ok 6 ok 7 ok 8 ok t/15_literal_param_constraints.t ......... 1..1 ok 1 ok t/16_cgi_object.t ........................ 1..2 ok 1 ok 2 ok t/17_multi_valued_keys.t ................. 1..8 ok 1 - inconditional filters still work with single values ok 2 - inconditional filters work with multi values ok 3 - field filters work with multiple values ok 4 - Test the filters applied to multiple values by RE work ok 5 - If any of the values fail the constraint, the field becomes invalid ok 6 - multi-valued field containing only undef should be missing ok 7 - multiple valued fields containing only undefined values should not be valid ok 8 - a single valued array should still trigger the dependency check ok t/18_constraint_refs.t ................... 1..4 ok 1 ok 2 - survived eval ok 3 ok 4 ok t/19_refs_as_values.t .................... 1..3 ok 1 ok 2 ok 3 ok t/20_careful_exception_handling.t ........ 1..1 ok 1 ok t/21_multiple_fields.t ................... 1..3 ok 1 ok 2 ok 3 ok t/25_results.t ........................... 1..7 ok 1 - using check() as class method ok 2 - valid() returns single value in scalar context ok 3 - valid() returns multi-valued results ok 4 - valid() returns single value in array context ok 5 - usg CODE references as default values ok 6 - defaults_regexp works (case 1) ok 7 - defaults_regexp works (case 1) ok t/26_qr.t ................................ ok 1 - using qr for regexp quoting ok 2 - using alternation with qr works ok 3 - expected to pass constraint ok 4 - expected to fail constraint ok 5 - field_filter_regexp_map ok 6 - named qr constraints ok 7 - untainting with qr 1..7 ok t/27_qualify_ref_happy_death.t ........... 1..5 ok 1 - happy filters typo failure ok 2 - happy field_filters typo failure ok 3 - happy field_filter_regexp_map typo failure ok 4 - happy constraints typo failure ok 5 - happy untainted constraints typo failure ok t/28_defaults_for_new.t .................. 1..3 ok 1 - defaults are checked for syntax ok 2 - testing defaults appearing in profile ok 3 - testing overriding defaults ok t/30_filter_definedness.t ................ ok 1 - basic validation generates no warnings with -w ok 2 - uninitialized value in filter_digit filter generates no warning ok 3 - uninitialized value in filter_dollars filter generates no warning ok 4 - uninitialized value in filter_quotemeta filter generates no warning ok 5 - uninitialized value in filter_integer filter generates no warning ok 6 - uninitialized value in filter_uc filter generates no warning ok 7 - uninitialized value in filter_pos_integer filter generates no warning ok 8 - uninitialized value in filter_neg_integer filter generates no warning ok 9 - uninitialized value in filter_lc filter generates no warning ok 10 - uninitialized value in filter_pos_decimal filter generates no warning ok 11 - uninitialized value in filter_decimal filter generates no warning ok 12 - uninitialized value in filter_neg_decimal filter generates no warning ok 13 - uninitialized value in filter_alphanum filter generates no warning ok 14 - uninitialized value in filter_phone filter generates no warning ok 15 - uninitialized value in filter_sql_wildcard filter generates no warning ok 16 - uninitialized value in filter_trim filter generates no warning ok 17 - uninitialized value in filter_strip filter generates no warning ok 18 - uninitialized value in filter_ucfirst filter generates no warning 1..18 ok t/FV_length.t ............................ ok 1 - use Data::FormValidator; ok 2 ok 3 - multiline FV_max_length in bounds ok 4 - multiline FV_max_length too long ok 5 - multiline FV_min_length in bounds ok 6 - multiline FV_min_length too short ok 7 - multiline FV_length_between in bounds ok 8 - multiline FV_length_between too short ok 9 - multiline FV_length_between too long ok 10 - identity alpha ok 11 - identity charlie ok 12 - identity echo ok 13 - long FV_max_length in bounds ok 14 - long FV_max_length too long ok 15 - long FV_min_length in bounds ok 16 - long FV_min_length too short ok 17 - long FV_length_between in bounds ok 18 - long FV_length_between too short ok 19 - long FV_length_between too long 1..19 ok t/any_errors.t ........................... ok 1 - [standard any_errors] good input passed ok 2 - [standard any_errors] no error messages ok 3 - [standard any_errors] bad input caught ok 4 - [standard any_errors] error messages reported ok 5 - [custom any_errors] good input passed ok 6 - [custom any_errors] no error messages ok 7 - [custom any_errors] 'some_errors' not reported ok 8 - [custom any_errors] bad input caught ok 9 - [custom any_errors] error messages reported ok 10 - [custom any_errors] 'some_errors' reported 1..10 ok t/check_profile_syntax.t ................. ok 1 - checking syntax of unknown msgs fields works ok 2 - checking syntax of constraint hashrefs works ok 3 - checking syntax of constraint_regexp_map hashrefs works 1..3 ok t/constraint_method.t .................... ok 1 - get_current_constraint_name works ok 2 - using qr with constraint_method fails as expected ok 3 - using qr with constraint_method succeeds as expected ok 4 - using qr with constraint_method_regexp_map fails as expected ok 5 - using qr with constraint_method_regexp_map succeeds as expected 1..5 ok t/constraint_method_string.t ............. 1..4 ok 1 - use Data::FormValidator; ok 2 - error thrown when given a string to constraint_method ok 3 - error thrown when given a string to constraint_method...even as part of a list. ok 4 - error thrown when given a string to constraint_method...even as hash declaration. ok t/constraint_method_zero.t ............... ok 1 - nine should be valid for 9 with capturing parens (untainted) ok 2 - nine should be valid for 9 without capturing parens (untainted) ok 3 - zero should be valid without capturing parens (untainted) ok 4 - zero should be valid with capturing parens (untainted) ok 5 - nine should be valid for 9 with capturing parens ok 6 - nine should be valid for 9 without capturing parens ok 7 - zero should be valid without capturing parens ok 8 - zero should be valid with capturing parens 1..8 ok t/constraint_regexp_map_profile_reuse.t .. ok 1 - constraints aren't duped when profile with constraint_regexp_map is reused ok 2 - constraints aren't duped when profile with constraint_regexp_map is reused ok 3 - field_filters aren't duped when profile with field_filter_regexp_map is reused ok 4 - field_filters aren't duped when profile with field_filter_regexp_map is reused 1..4 ok t/constraints_builtin.t .................. ok 1 - survived validate ok 2 - using 0 in a constraint regexp works 1..2 ok t/constraints_builtin_closure.t .......... ok 1 - survived eval ok 2 - using 0 in a constraint regexp works ok 3 - set_current_contraint_name succeeds ok 4 - name_this succeeds ok 5 - set_current_contraint_name doesn't work if you typo it 1..5 ok t/constraints_factory.t .................. 1..4 ok 1 - use Data::FormValidator; ok 2 - use Data::FormValidator::ConstraintsFactory; ok 3 - positive test for make_length_constraint() ok 4 - negative test for make_length_constraint() ok t/constraints_invalid_once_only.t ........ 1..1 ok 1 - constraint marked as invalid only once ok t/constraints_regexp_map_interaction.t ... ok 1 - Survived validate ok 2 - Correctly catches the bad field ok 3 - The invalid field is listed correctly as 'email_field' ok 4 - Survived validate ok 5 - Still correctly catches the bad field ok 6 - The invalid field is still listed correctly as 'email_field' ok 7 - But perl agrees that the email address does match the regex 1..7 ok t/constraints_reuse.t .................... 1..7 ok 1 ok 2 ok 3 ok 4 ok 5 - first constraint applied intentionally fails ok 6 - second constraint still has access to value of field used in first failed constraint. ok 7 - no warnings emitted ok t/credit_card.t .......................... 1..25 ok 1 - Invalid: Discover/6000111122223333 (old) ok 2 - Valid: Discover/6011111111111117 (old) ok 3 - Valid: Discover/6011000990139424 (old) ok 4 - Invalid: Amex/371500001111222 (old) ok 5 - Valid: Amex/378282246310005 (old) ok 6 - Valid: Amex/371449635398431 (old) ok 7 - Invalid: Visa/4000111122223333 (old) ok 8 - Valid: Visa/4111111111111111 (old) ok 9 - Valid: Visa/4012888888881881 (old) ok 10 - Invalid: Mastercard/5424111122223333 (old) ok 11 - Valid: Mastercard/5105105105105100 (old) ok 12 - Valid: Mastercard/5555555555554444 (old) ok 13 - cc_number subroutine runs without error ok 14 - Invalid: Discover/6000111122223333 (new) ok 15 - Valid: Discover/6011111111111117 (new) ok 16 - Valid: Discover/6011000990139424 (new) ok 17 - Invalid: Amex/371500001111222 (new) ok 18 - Valid: Amex/378282246310005 (new) ok 19 - Valid: Amex/371449635398431 (new) ok 20 - Invalid: Visa/4000111122223333 (new) ok 21 - Valid: Visa/4111111111111111 (new) ok 22 - Valid: Visa/4012888888881881 (new) ok 23 - Invalid: Mastercard/5424111122223333 (new) ok 24 - Valid: Mastercard/5105105105105100 (new) ok 25 - Valid: Mastercard/5555555555554444 (new) ok t/dates.t ................................ ok 1 - returning untainted date ok 2 - basic date prepare and parse test ok 3 ok 4 ok 5 ok 6 ok 7 ok 8 - returning untainted date ok 9 - basic date prepare and parse test ok 10 - month ok 11 - day ok 12 - hour ok 13 - min ok 14 - sec ok 15 - eval ok 16 - expecting date_and_time success ok 17 - expecting date_and_time failure ok 18 - returning date ok 19 - basic date prepare and parse test ok 20 ok 21 1..21 ok t/dates_closure.t ........................ ok 1 - returning untainted date ok 2 - basic date prepare and parse test ok 3 ok 4 ok 5 ok 6 ok 7 ok 8 - returning untainted date ok 9 - basic date prepare and parse test ok 10 - month ok 11 - day ok 12 - hour ok 13 - min ok 14 - sec ok 15 - eval ok 16 - expecting date_and_time success ok 17 - expecting date_and_time failure ok 18 - 02/29/2008 should pass MM/DD/YY(?:YY)? not ok 19 - 02/29/1976 should pass MM/DD/YY(?:YY)? # TODO leap year bug? # Failed (TODO) test '02/29/1976 should pass MM/DD/YY(?:YY)?' # at t/dates_closure.t line 94. ok 20 - 02/29/2008 should fail MM/DD/YYY?Y? 1..20 ok t/dependency_coderef.t ................... 1..18 ok 1 - checking that dependency coderef is called ok 2 - code was called ok 3 - code received 2 args ok 4 - received correct value ok 5 - received dfv object ok 6 - dfv object isa Data::FormValidator::Results ok 7 - checking a value that has a depenency ok 8 - returned object isa Data::FormValidator::Results ok 9 - has_missing returned true ok 10 - missing('cc_cvv') returned true ok 11 - checking a value that has no dependencies ok 12 - returned object isa Data::FormValidator::Results ok 13 - has_missing returned false ok 14 - missing('cc_cvv') returned false ok 15 - checking multiple values ok 16 - returned object isa Data::FormValidator::Results ok 17 - has_missing returned true ok 18 - missing('cc_cvv') returned true ok t/dependency_groups.t .................... ok 1 - no eval problems ok 2 - [pass1] valid ok 3 - missing [pass2] ok 4 - no eval problems ok 5 - returned object isa Data::FormValidator::Results ok 6 - has_missing returned true ok 7 - missing(pass2) returned true ok 8 - missing(pass1) returned false ok 9 - valid(pass1) returned true ok 10 - valid(pass2) returned true ok 11 - no eval problems ok 12 - returned object isa Data::FormValidator::Results ok 13 - has_missing returned true ok 14 - missing(pass2) returned true ok 15 - missing(pass1) returned false ok 16 - valid(pass1) returned true ok 17 - valid(pass2) returned true ok 18 - no eval problems ok 19 - [pass2] valid ok 20 - missing [pass1] ok 21 - no eval problems ok 22 - returned object isa Data::FormValidator::Results ok 23 - has_missing returned true ok 24 - missing(pass1) returned true ok 25 - missing(pass2) returned false ok 26 - valid(pass2) returned true ok 27 - valid(pass1) returned true ok 28 - no eval problems ok 29 - returned object isa Data::FormValidator::Results ok 30 - has_missing returned true ok 31 - missing(pass1) returned true ok 32 - missing(pass2) returned false ok 33 - valid(pass2) returned true ok 34 - valid(pass1) returned true 1..34 ok t/filter_constraints.t ................... 1..4 ok 1 - all fields are valid ok 2 - survived eval ok 3 - when passed through param, local filters are applied. ok 4 - when passed through param, global filters are applied. ok t/filters_builtin.t ...................... ok 1 - FV_split with two values ok 2 - FV_split with one value ok 3 - FV_split with no values ok 4 - FV_replace positive test ok 5 - FV_replace negative test ok 6 - filter_dollars works as expected not ok 7 - filter_dollars removes trailing numbers # TODO all these broken filters need to be dealt with. # Failed (TODO) test 'filter_dollars removes trailing numbers' # at t/filters_builtin.t line 26. # got: '0.111' # expected: '0.11' not ok 8 - filter_neg_integer should leave string without a negative integer alone. # TODO all these broken filters need to be dealt with. # Failed (TODO) test 'filter_neg_integer should leave string without a negative integer alone.' # at t/filters_builtin.t line 30. # got: '9-' # expected: 'a9-' not ok 9 - filter_pos_integer should care which side a + is on. # TODO all these broken filters need to be dealt with. # Failed (TODO) test 'filter_pos_integer should care which side a + is on.' # at t/filters_builtin.t line 34. # got: '9+' # expected: '9' not ok 10 - filter_integer should care which side a + is on. # TODO all these broken filters need to be dealt with. # Failed (TODO) test 'filter_integer should care which side a + is on.' # at t/filters_builtin.t line 38. # got: '9+' # expected: '9' not ok 11 - filter_decimal should handle commas correctly # TODO all these broken filters need to be dealt with. # Failed (TODO) test 'filter_decimal should handle commas correctly' # at t/filters_builtin.t line 42. # got: '1.000.23' # expected: '1000.23' not ok 12 - filter_pos_decimal should handle commas correctly # TODO all these broken filters need to be dealt with. # Failed (TODO) test 'filter_pos_decimal should handle commas correctly' # at t/filters_builtin.t line 46. # got: '1.000.23' # expected: '1000.23' not ok 13 - filter_neg_decimal should handle commas correctly # TODO all these broken filters need to be dealt with. # Failed (TODO) test 'filter_neg_decimal should handle commas correctly' # at t/filters_builtin.t line 50. # got: '-1.000.23' # expected: '-1000.23' 1..13 ok t/filters_shouldnt_modify.t .............. ok 1 - after copying structure, values should have different memory addresses ok 2 - filters shouldn't modify data in arrayrefs 1..2 ok t/get_filtered_data.t .................... 1..4 ok 1 - get_filtered_data works for empty hashref ok 2 - get_filtered_data returns correct filtered data ok 3 - password valid ok 4 - confirm valid ok t/get_input_data.t ....................... ok 1 - get_input_data works for empty hashref ok 2 - get_input_data works for CGI object ok 3 - get_input_data( as_hashref => 1 ) works for CGI object 1..3 ok t/missing_optional.t ..................... ok 1 - survived eval ok 2 ok 3 ok 4 ok 5 ok 6 ok 7 - optional fields have to at least exist to be valid ok 8 - optional_invalid is invalid ok 9 - optional_invalid is not valid 1..9 ok t/msgs.t ................................. ok 1 ok 2 - existence of msgs method ok 3 - invalid fields returned as hash in simple case ok 4 - default invalid message ok 5 - default missing message ok 6 - default formatting ok 7 - survived eval ok 8 - multiple constraints constraint definition ok 9 - survived eval ok 10 - using default prefix ok 11 - size of msgs hash ok 12 - any_errors ok 13 - passing controls to method ok 14 - calling msgs method without hash definition ok 15 - Spelling "separator" correctly should work OK. ok 16 - A callback can be used for msgs 1..16 ok t/multiple_constraints.t ................. 1..8 ok 1 - survived eval ok 2 ok 3 ok 4 ok 5 ok 6 - expect 'multiple' not to appear in valid ok 7 - list of failed constraints for 'multiple' ok 8 - single is valid ok t/params_not_mentioned.t ................. 1..5 ok 1 - no_invalids ok 2 - foo valid ok 3 - survived eval ok 4 - no_invalids ok 5 - foo valid ok t/pod.t .................................. 1..14 ok 1 - POD test for blib/lib/Data/FormValidator.pm ok 2 - POD test for blib/lib/Data/FormValidator/Constraints.pm ok 3 - POD test for blib/lib/Data/FormValidator/ConstraintsFactory.pm ok 4 - POD test for blib/lib/Data/FormValidator/Filters.pm ok 5 - POD test for blib/lib/Data/FormValidator/Results.pm ok 6 - POD test for blib/lib/Data/FormValidator/Constraints/Upload.pm ok 7 - POD test for blib/lib/Data/FormValidator/Constraints/Dates.pm ok 8 - POD test for lib/Data/FormValidator.pm ok 9 - POD test for lib/Data/FormValidator/Constraints.pm ok 10 - POD test for lib/Data/FormValidator/ConstraintsFactory.pm ok 11 - POD test for lib/Data/FormValidator/Filters.pm ok 12 - POD test for lib/Data/FormValidator/Results.pm ok 13 - POD test for lib/Data/FormValidator/Constraints/Upload.pm ok 14 - POD test for lib/Data/FormValidator/Constraints/Dates.pm ok t/procedural_valid.t ..................... ok 1 ok 2 ok 3 ok 4 ok 5 ok 6 ok 7 ok 8 ok 9 ok 10 ok 11 ok 12 ok 13 ok 14 ok 15 ok 16 ok 17 ok 18 ok 19 ok 20 ok 21 ok 22 ok 23 ok 24 ok 25 ok 26 ok 27 ok 28 - semi-colons in e-mail aren't valid ok 29 - spaces in e-mail aren't valid ok 30 - including a null in an e-mail is not valid. ok 31 - 'mark' is not a valid e-mail ok 32 - 'Mark Stosberg ' is not a valid e-mail ok 33 - 'mark@summersault.com' is a valid e-mail ok 34 - 'Mark.Stosberg@summersault.com' is a valid e-mail ok 35 - 'Mark_Stosberg@summersault.com' is a valid e-mail ok 36 - 'Mark_O'Doul@summersault.com' is a valid e-mail 1..36 ok t/profile_checking.t ..................... 1..1 ok 1 ok t/regexp_common.t ........................ 1..10 ok 1 - runtime errors ok 2 - good ip ok 3 - bad ip ok 4 - runtime errors ok 5 - good ip with tainting ok 6 - bad ip with tainting ok 7 - runtime errors ok 8 - expecting success with params ok 9 - expecting failure with params ok 10 - testing that the RE must match from end-to-end ok t/regexp_common_closure.t ................ 1..13 ok 1 - use Data::FormValidator::Constraints; ok 2 - survived eval ok 3 - good ip ok 4 - bad ip ok 5 - zero is valid int ok 6 - survived eval ok 7 - good ip with tainting ok 8 - bad ip with tainting ok 9 - zero is valid int with untainting ok 10 - runtime errors ok 11 - expecting success with params ok 12 - expecting failure with params ok 13 - testing that the RE must match from end-to-end ok t/results_success.t ...................... 1..4 ok 1 - success with unknown ok 2 - returns true in bool context on success ok 3 - not success() ok 4 - returns false in bool context on not success ok t/simple.t ............................... 1..3 ok 1 - survived eval ok 2 - phone is valid ok 3 ok t/tt_and_overload.t ...................... 1..1 ok 1 ok t/undefined_arrayref.t ................... 1..1 ok 1 - no invalid fields are returned as an arrayref ok t/unknown.t .............................. 1..4 ok 1 - using check() as class method ok 2 - unknown() returns single value in scalar context ok 3 - unknown() returns multi-valued results ok 4 - unknown() returns single value in array context ok t/untaint.t .............................. 1..55 ok 1 - avoided eval error ok 2 - found firstname ok 3 - firstname is untainted ok 4 - firstname has expected value ok 5 - avoided eval error ok 6 ok 7 ok 8 ok 9 ok 10 ok 11 ok 12 ok 13 - email2 is tainted ok 14 ok 15 - survived eval ok 16 - found email1 in %valid ok 17 - email one is not tainted ok 18 - email1 identity ok 19 ok 20 ok 21 ok 22 ok 23 - cats_name is not valid ok 24 - cats_name fails constraint ok 25 ok 26 ok 27 ok 28 - avoided eval error ok 29 - zip_field1 should be untainted ok 30 - zip_field2 should be tainted ok 31 - qr RE without parens in untainted ok 32 - qr RE with parens in untainted ok 33 - avoided eval error ok 34 - zip_field1 should be valid ok 35 - zip_field1 should be untainted ok 36 - zip_field2 should be valid ok 37 - zip_field2 should be untainted ok 38 - avoided eval error ok 39 - zip_field1 should be valid ok 40 - zip_field1 should be untainted ok 41 - zip_field2 should be valid ok 42 - zip_field2 should be untainted ok 43 - email1 should be valid ok 44 - email1 should be untainted ok 45 - email2 should be valid ok 46 - email2 should be untainted ok 47 - avoided eval error ok 48 - zip_field1 should be valid ok 49 - zip_field1 should be untainted ok 50 - zip_field2 should be valid ok 51 - zip_field2 should be untainted ok 52 - email1 should be valid ok 53 - email1 should be untainted ok 54 - email2 should be valid ok 55 - email2 should be untainted ok # Adding CGI::Simple tests # testing with CGI.pm version: 3.48 # testing with CGI::Simple version: 1.112 # Running tests with CGI # Running tests with CGI::Simple t/upload.t ............................... ok 1 - use CGI; ok 2 - use Data::FormValidator::Constraints::Upload; ok 3 - survived eval ok 4 - expect format failure ok 5 - expect non-existent failure ok 6 - Make sure 100x100 passes because it is the right type and size ok 7 - meta() returns hash ref ok 8 - setting extension meta data ok 9 - setting mime_type meta data ok 10 - 300x300 should fail because it exceeds max_bytes ok 11 - CGI: setting bytes meta data ok 12 ok 13 - expecting success with max_dimensions ok 14 - expecting failure with max_dimensions ok 15 - setting width as meta data ok 16 - setting height as meta data ok 17 - expecting success with max_dimensions using constraint_regexp_map ok 18 - expecting failure with max_dimensions using constraint_regexp_map ok 19 ok 20 - expecting success with min_dimensions ok 21 - expecting failure with min_dimensions ok 22 ok 23 - expecting success with mime_type ok 24 - expecting failure with mime_type ok 25 - survived eval ok 26 - expecting failure with size range ok 27 - expecting success with size range ok 28 - survived eval ok 29 - expect format failure ok 30 - expect non-existent failure ok 31 - Make sure 100x100 passes because it is the right type and size ok 32 - meta() returns hash ref ok 33 - setting extension meta data ok 34 - setting mime_type meta data ok 35 - 300x300 should fail because it exceeds max_bytes ok 36 - CGI::Simple: setting bytes meta data ok 37 ok 38 - expecting success with max_dimensions ok 39 - expecting failure with max_dimensions ok 40 - setting width as meta data ok 41 - setting height as meta data ok 42 - expecting success with max_dimensions using constraint_regexp_map ok 43 - expecting failure with max_dimensions using constraint_regexp_map ok 44 ok 45 - expecting success with min_dimensions ok 46 - expecting failure with min_dimensions ok 47 ok 48 - expecting success with mime_type ok 49 - expecting failure with mime_type ok 50 - survived eval ok 51 - expecting failure with size range ok 52 - expecting success with size range 1..52 ok # testing with CGI.pm version: 3.48 t/upload_closure.t ....................... ok 1 - use CGI; ok 2 - use Data::FormValidator::Constraints::Upload; ok 3 - survived eval ok 4 - expect format failure ok 5 - expect non-existent failure ok 6 ok 7 - meta() returns hash ref ok 8 - setting extension meta data ok 9 - setting mime_type meta data ok 10 - max_bytes ok 11 - setting bytes meta data ok 12 - survived eval ok 13 - expecting success with max_dimensions ok 14 - expecting failure with max_dimensions ok 15 - setting width as meta data ok 16 - setting height as meta data ok 17 - expecting success with max_dimensions using constraint_regexp_map ok 18 - expecting failure with max_dimensions using constraint_regexp_map 1..18 ok t/upload_mime_types.t .................... 1..5 ok 1 - use Data::FormValidator::Constraints::Upload; ok 2 - 'foo' not considered an allowed mime type ok 3 - 'image/jpeg' is considered an allowed mime type ok 4 - 'image/JPEG' is considered an allowed mime type ok 5 - 'image/pjpeg' is considered an allowed mime type ok All tests successful. Files=62, Tests=625, 4 wallclock secs ( 0.17 usr 0.01 sys + 3.26 cusr 0.19 csys = 3.63 CPU) Result: PASS MARKSTOS/Data-FormValidator-4.65.tar.gz ./Build test verbose=1 -- OK Mark Stosberg <mark@summersault.com> Validates user input (usually from an HTML form) based on input profile. >>> (cd /home/fly818/var/cpan/build/Data-FormValidator-4.65-Z91eKF && tar cvf - Data-FormValidator-4.65.ppd blib) | gzip -c >/home/fly818/var/REPO/M/MA/MARKSTOS/Data-FormValidator-4.65.tar.gz Data-FormValidator-4.65.ppd blib/ blib/lib/ blib/lib/Data/ blib/lib/Data/FormValidator/ blib/lib/Data/FormValidator/Constraints.pm blib/lib/Data/FormValidator/ConstraintsFactory.pm blib/lib/Data/FormValidator/Filters.pm blib/lib/Data/FormValidator/Results.pm blib/lib/Data/FormValidator/Constraints/ blib/lib/Data/FormValidator/Constraints/Upload.pm blib/lib/Data/FormValidator/Constraints/Dates.pm blib/lib/Data/FormValidator.pm >>> mv /home/fly818/var/cpan/build/Data-FormValidator-4.65-Z91eKF/Data-FormValidator-4.65.ppd /home/fly818/var/REPO/M/MA/MARKSTOS Finished 2009-12-31T04:05:17