From: Steve Loughran <steve_loughran@hp...> - 2004-03-02 16:33:26
I have just committed changes to the test harness so that
1. it starts the daemon before the tests are run, if needed
2. it stops the daemon if it was started by ant
3. it has some pauses to handle startup delay.
the result is that you can run the system tests and they will start up a
system, but you can also start up a daemon under a debugger, set
breakpoints, etc, and the tests will run against that daemon.
To do all of this the testharness uses the ant tasks, which need to be
built before running the harness. It'll complain if you forget, with a
helpful error message.
I have set up the core/build.xml so that the line
ant clean dist test
is enough to do a clean distribution and and test; the test target
depends on one called 'tasks' that creates the tasks; "ant tasks" is
sufficient to create the tasks themselves.
The test target in core/build.xml now does
-parser validation of .sf files in smartfrog/src
-ant tests (if ant-testutils.jar is found)
The ant and testharness test results go into different places, but
cruise control is configured to fetch everything into one place.
I have not made any attempt to bring this into gump, as now that gump is
working I want to leave that for a few days. I also need to add
documentation to the tasks; I want to use some ant autogenerating stuff
to do that, but it gets confused (!) by deep inheritance graphs, which
is what the smartfrog ant tasks have.
For now, look at extras/ant/test/files to see different tasks in action
Get latest updates about Open Source Projects, Conferences and News.