On Sun, Dec 4, 2011 at 7:59 PM, Dimitar Petrov <mita...@gmail.com> wrote:

> You might want to check this blog post also:
> http://www.modernperlbooks.com/mt/2011/11/parallelism-and-test-suites.html


thanks, but that's what got me into this mess.. well
http://www.modernperlbooks.com/mt/2011/12/controlling-test-parallelism-with-prove.html
which
also links to that..

ok, actually I've tidied up the mess and I'm rather pleased with how it
looks.. I'm going to have a lot more tests than this by the time I'm
finished so I think it's been well worth the effort.. (note the wallclock
secs)

$ prove Lecstor/t BB/t BB-Site-Catalyst/t aid_proxy/AID-Proxy/t
...
All tests successful.
Files=29, Tests=369, 109 wallclock secs ( 0.15 usr  0.04 sys + 26.25 cusr
 4.36 csys = 30.80 CPU)


$ prove -j9 Lecstor/t BB/t BB-Site-Catalyst/t aid_proxy/AID-Proxy/t
...
All tests successful.
Files=29, Tests=369, 19 wallclock secs ( 0.18 usr  0.04 sys + 34.14 cusr
 4.98 csys = 39.34 CPU)


cheers,

J



> Cheers
>
> On Sun, Dec 4, 2011 at 10:49 AM, Jason Galea <li...@eightdegrees.com.au>wrote:
>
>> On Sun, Dec 4, 2011 at 7:10 PM, Tomas Doran <bobtf...@bobtfish.net>wrote:
>>>
>>>>
>>>> On 4 Dec 2011, at 04:13, Jason Galea wrote:
>>>>
>>>>  hmm.. actually.. can I hand Catalyst::Test the schema I can get from
>>>>> Test::DBIx::Class?
>>>>>
>>>>
>>>> I think you can just force replace the schema, with something like
>>>> MyApp->model('DB')->schema($**mytestschema);
>>>>
>>>
>> yup, works a treat.. thanks again.
>>
>> $ prove t
>> ...
>> All tests successful.
>> Files=6, Tests=90, 27 wallclock secs ( 0.07 usr  0.02 sys +  9.87 cusr
>>  1.14 csys = 11.10 CPU)
>>
>> Result: PASS
>>
>> $ prove -j9 t
>> ...
>> All tests successful.
>> Files=6, Tests=90,  8 wallclock secs ( 0.06 usr  0.01 sys + 11.24 cusr
>>  1.34 csys = 12.65 CPU)
>>
>> Result: PASS
>>
>> woohoo!
>>
>>
>>
>>
>>>
>>>> Alternatively, you can setup a test config (by writing out a config
>>>> file with the extra DB details in) before using Catalyst::Test (although
>>>> N.B. that use Catalyst::Test will happen at compile time, so you probably
>>>> need the initial setup in a BEGIN block).
>>>>
>>>> Cheers
>>>> t0m
>>>>
>>>>
>>>> ______________________________**_________________
>>>> List: Catalyst@lists.scsys.co.uk
>>>> Listinfo: 
>>>> http://lists.scsys.co.uk/cgi-**bin/mailman/listinfo/catalyst<http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst>
>>>> Searchable archive: http://www.mail-archive.com/**
>>>> catalyst@lists.scsys.co.uk/<http://www.mail-archive.com/catalyst@lists.scsys.co.uk/>
>>>> Dev site: http://dev.catalyst.perl.org/
>>>>
>>>
>>>
>>
>> _______________________________________________
>> List: Catalyst@lists.scsys.co.uk
>> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
>> Searchable archive:
>> http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
>> Dev site: http://dev.catalyst.perl.org/
>>
>>
>
> _______________________________________________
> List: Catalyst@lists.scsys.co.uk
> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
> Searchable archive:
> http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
> Dev site: http://dev.catalyst.perl.org/
>
>
_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

Reply via email to