Hi Ruslan:
I tested the .t file against github Jifty::DBI.
The result of "prove -vl t/Jifty-DBI-02searches_distinct_values.t" is:
t/Jifty-DBI-02searches_distinct_values.t ..
1..94
ok 1 - The object isa DBI::db
# using 'TestApp::schema_sqlite' schema for SQLite
ok 2 - Inserted the schema. got a statement handle back isa DBI::st
ok 3 - init users data
ok 4 - init groups data
ok 5 - init users&groups relations data
ok 6 - after Clone looks the same
# distinct_column_values on clean
ok 7 - full on non limitted collection
ok 8 - sorting in DB
ok 9 - reverse sorting in DB
ok 10 - sorting and limitted
ok 11 # skip ENV is not defined for driver 'mysql'
ok 12 # skip ENV is not defined for driver 'mysql'
ok 13 # skip ENV is not defined for driver 'mysql'
ok 14 # skip ENV is not defined for driver 'mysql'
ok 15 # skip ENV is not defined for driver 'mysql'
ok 16 # skip ENV is not defined for driver 'mysql'
ok 17 # skip ENV is not defined for driver 'mysql'
ok 18 # skip ENV is not defined for driver 'mysql'
ok 19 # skip ENV is not defined for driver 'mysql'
ok 20 # skip ENV is not defined for driver 'mysql'
ok 21 # skip ENV is not defined for driver 'mysql'
ok 22 # skip ENV is not defined for driver 'mysql'
ok 23 # skip ENV is not defined for driver 'mysql'
ok 24 # skip ENV is not defined for driver 'mysql'
ok 25 # skip ENV is not defined for driver 'mysql'
ok 26 # skip ENV is not defined for driver 'mysql'
ok 27 # skip ENV is not defined for driver 'mysql'
ok 28 # skip ENV is not defined for driver 'mysql'
ok 29 # skip ENV is not defined for driver 'mysql'
ok 30 # skip ENV is not defined for driver 'mysql'
ok 31 # skip ENV is not defined for driver 'mysql'
ok 32 # skip ENV is not defined for driver 'mysql'
ok 33 # skip ENV is not defined for driver 'mysql'
ok 34 # skip ENV is not defined for driver 'mysql'
ok 35 # skip ENV is not defined for driver 'mysql'
ok 36 # skip ENV is not defined for driver 'mysql'
ok 37 # skip ENV is not defined for driver 'mysql'
ok 38 # skip ENV is not defined for driver 'mysql'
ok 39 # skip ENV is not defined for driver 'mysql'
ok 40 # skip ENV is not defined for driver 'mysql'
ok 41 # skip ENV is not defined for driver 'mysql'
ok 42 # skip ENV is not defined for driver 'mysql'
ok 43 # skip ENV is not defined for driver 'mysql'
ok 44 # skip ENV is not defined for driver 'mysql'
ok 45 # skip ENV is not defined for driver 'mysql'
ok 46 # skip ENV is not defined for driver 'mysql'
ok 47 # skip ENV is not defined for driver 'mysql'
ok 48 # skip ENV is not defined for driver 'mysql'
ok 49 # skip ENV is not defined for driver 'mysql'
ok 50 # skip ENV is not defined for driver 'mysql'
ok 51 # skip ENV is not defined for driver 'mysql'
ok 52 # skip ENV is not defined for driver 'mysql'
ok 53 # skip ENV is not defined for driver 'mysql'
ok 54 # skip ENV is not defined for driver 'mysql'
ok 55 # skip ENV is not defined for driver 'mysql'
ok 56 # skip ENV is not defined for driver 'mysql'
ok 57 # skip ENV is not defined for driver 'mysql'
# Looks like you planned 94 tests but ran 57.
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 37/94 subtests
(less 47 skipped subtests: 10 okay)
Test Summary Report
-------------------
t/Jifty-DBI-02searches_distinct_values.t (Wstat: 65280 Tests: 57 Failed: 0)
Non-zero exit status: 255
Parse errors: Bad plan. You planned 94 tests but ran 57.
Files=1, Tests=57, 1 wallclock secs ( 0.06 usr 0.00 sys + 0.20 cusr 0.01
csys = 0.27 CPU)
Result: FAIL
BR
Jes
El Thu, 3 Jun 2010 23:09:10 +0400
Ruslan Zakirov <r...@bestpractical.com> escribió:
> On Thu, Jun 3, 2010 at 8:15 PM, Jes <jjje...@gmail.com> wrote:
> > Hi Ruslan:
> >
> > I tested your new patch and it doesn't work with my app. Now it
> > seems it enters in a non-end-loop.
>
> The only idea I have at the moment is that I used something that works
> in Jifty-DBI from repository and doesn't work in older versions.
>
> > I couldn't test the .t test because of:
> >
> > * I'm not sure about run jifty tests
> > * "BEGIN { require "t/utils.pl" }" this file is missing in my t
> > directory
>
> Test file is for t/ dir from tarball/repository. Download Jifty-DBI
> from CPAN or clone from github and put file into t/ dir. You can
> either use `make test` or `prove -vl t/xxxx.t` for testing.
>
> If you can demonstrate problem in .t file it would help me a lot.
>
> > More help would be apreciated :D. Thanks for your patience.
> >
> > BR
> >
> > Jes
>
_______________________________________________
jifty-devel mailing list
jifty-devel@lists.jifty.org
http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel
