[Catalyst] reducing app startup time in tests

[Matt S Trout]

On 12 Jul 2006, at 13:55, Richard Jolly wrote:
> Hi,
>
> We have a fair number of tests using  
> Test::WWW::Mechanize::Catalyst. The startup time in these is slow  
> enough (approx 20 seconds) that it is inconvenient for development,  
> because our total test run is almost 1 hr.
>
> Most of these tests have identical setup actions, and do not alter  
> the db they run against.
>
> The hardware is sub par, which is one obvious way to address this.  
> Another would be to start a server and run the tests against that.  
> Are there others? Something clever like using Storable to freeze  
> the initialized Catalyst app to disk, and have the test setup  
> simply retrieve it?
Wouldn't it be easier simply to have a copy of the test server fired  
up at the beginning of a test run and then use the CATALYST_SERVER  
environment variable to make Catalyst::Test (and hence TWM::C) run  
against this rather than an embedded copy?

-- 
Matt S Trout, Technical Director, Shadowcat Systems Ltd.
Offering custom development, consultancy and support contracts for  
Catalyst,
DBIx::Class and BAST. Contact mst (at) shadowcatsystems.co.uk for  
details.
+ Help us build a better perl ORM: http://dbix- 
class.shadowcatsystems.co.uk/ +