byterock

Test postette day again here in the Moose Pen.

Time to re-run my tests suites again to check the 'Sate of the Onion' before I move on. I expect this will be a very short post.

For Database::Accessor as expected I did not have many changes since last week

 2 files changed, 70 insertions(+), 24 deletions(-)

and the test run was;

All tests successful.

Files=29, Tests=490, 81 wallclock secs ( 0.23 usr  0.06 sys + 77.55 cusr  1.71 csys = 79.55 CPU)

Result: PASS

Now Driver::DBI which had a modest number of changes;

 6 files changed, 358 insertions(+), 45 deletions(-)

and the test results for it are;

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

  Non-zero exit status: 255

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

t/30_where_basic.t    (Wstat: 768 Tests: 86 Failed: 6)

  Failed tests:  81-86

  Non-zero exit status: 3

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

t/60_order_by.t       (Wstat: 256 Tests: 22 Failed: 1)

  Failed test:  21

so not much there a few bad plans and a few fails; The fails all being in the expected SQL like this one

Expected  WHERE CASE WHEN Price < ? THEN ? WHEN Price >= ? AND Price <= ?

Generated WHERE CASE WHEN people.Price < ? THEN ? WHEN people.Price >= ?

I guess I forgot to update my expected SQL.

After a few mins of updates a quick check in and then a pull of

3 files changed, 6 insertions(+), 6 deletions(-)

My test suite now returns;

All tests successful.

Files=11, Tests=454, 29 wallclock secs ( 0.18 usr  0.02 sys + 27.90 cusr  1.01 csys = 29.11 CPU)

Result: PASS

So sitting pretty for this week.