byterock

Its test post-ette day again here in the Moose-Pen

I guess I am following a very predictable pattern The weekend is here and I just do a post on test results. Well why spoil a good thing?

Since my last test round I have changed a good number of things about but I am fairly sure that Database::Accessor is in good shape though I am not looking forward to see what sort of state Driver ::DBI is in.

As I suspected there was only very minor problems with Database::Accessor;

Looks like you planned 2 tests but ran 6.

t/15_case.t ................. Dubious, test returned

I just have to update that test count and now I get

All tests successful.

Files=29, Tests=452, 77

ok onto Driver::DBI

Opps! as I expected things are not looking that good

t/22_fields_extended.t (Wstat: 65280 Tests: 0 Failed: 0)

  Non-zero exit status: 255

  Parse errors: Bad plan.  You planned 88 tests but ran 0.

t/30_where_basic.t    (Wstat: 3840 Tests: 80 Failed: 15)

  Failed tests:  19, 21, 23, 27, 29, 31, 59, 61, 63, 67

                69, 71, 75, 77, 79

  Non-zero exit status: 15

t/32_where_operators.t (Wstat: 768 Tests: 130 Failed: 53)

  Failed tests:  41, 43, 45, 81-130

  Non-zero exit status: 3

  Parse errors: Bad plan.  You planned 80 tests but ran 130.

t/40_joins.t          (Wstat: 768 Tests: 40 Failed: 3)

  Failed tests:  35, 37, 39

  Non-zero exit status: 3

t/50_group_by.t       (Wstat: 768 Tests: 34 Failed: 3)

  Failed tests:  9, 23, 30

  Non-zero exit status: 3

t/60_order_by.t       (Wstat: 512 Tests: 20 Failed: 8)

  Failed tests:  9, 14-20

  Non-zero exit status: 2

  Parse errors: Bad plan.  You planned 13 tests but ran 20.

t/90_extened.t        (Wstat: 65280 Tests: 0 Failed: 0)

  Non-zero exit status: 255

  Parse errors: Bad plan.  You planned 11 tests but ran 0

and I do not like that 'Non-zero exit status: 255' I am getting and that one should be the first one I look at but I can ignore test case '22_fields_extended.t' for now as that is my test for 'case' statements and I am still working on that.

The next case '30_where_baisc.t' I found that all 15 fails where like this one

# Expected SQL-->WHERE substr(people.username,?,?) = ?

# Generated SQL->WHERE SUBSTR(people.username,?,?) = ?

a simple fix on the 'expected' SQL to match up the case of the 'substr' function, now that I have them coming from the Database::Driver in 'upper case'.

After a bunch of rounds of 'find and replace' I ended up with some 26 changes to all my test files. I checked that in and ran my tests again;

t/32_where_operators.t (Wstat: 65280 Tests: 130 Failed: 50)

  Failed tests:  81-130

  Non-zero exit status: 255

  Parse errors: Bad plan.  You planned 80 tests but ran 130.

t/60_order_by.t       (Wstat: 65280 Tests: 20 Failed: 7)

  Failed tests:  14-20

  Non-zero exit status: 255

  Parse errors: Bad plan.  You planned 13 tests but ran 20.

so now only clean up a few test counts and a removal of that 22_fields_extended.t case I get

All tests successful.

Files=10, Tests=436,

now I am free for the day.