That might work, but I think what I'd rather do is just create a one TestSuite that does the setup beforehand, then run the tests. I have noticed that maven seems to run the tests based on a naming convention, *Test.java gets run, but *Tests.java don't. Can I override this somehow? I'd like to make it so that only one specific test suite gets called, like AllTests.java, but then none of the other test get called. I suppose I could just call my test suite FullTest.java, and then name all my tests WhateverTests.java, but I'd like to explicitly define it if it is possible.
On 11/8/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
Assuming you're using Maven2... Have you looked at the complete list of phases? http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html Sounds to me like you might want to use @process-test-resources. Wayne On 11/7/06, Paul Barry <[EMAIL PROTECTED]> wrote: > Is there a way to perform a task before a goal executes? Specifically > what I'm looking to do is load data into my test database before all > my tests run. I'm using Spring's > AbstractTransactionalDataSourceSpringContextTests, which rolls back > all changes after each test, so that I don't have to re-load the data > after every test. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
