indeed, this works fine. Some code for those that are curious:
in t/test_setup.pm:
package test_setup;
sub setup {
# setup your db or whatever here
}
1;
In a test module
require t::test_setup;
test_setup::setup();
Rather simple in fact. Works fine on 5.10
UPDATE: in fact - I am using this.
package test_setup;
sub setup {
# ...
}
BEGIN { # must be after the sub definition
setup();
$ENV{USE_TEST_DB} = 1;
}
1;
And in my Catalyst MyApp.pm class:
if ( $ENV{USE_TEST_DB} ) {
__PACKAGE__->config( 'Plugin::ConfigLoader' => { file => 'myapp_test
+.yml'} );
}
Now it is only necessary to "use" test_setup.pm. The setup is executed automatically, and the ENV variable causes the Catalyst app to use another config, which in turn connects to the test database in place of the normal development one.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|