Thanks for the links! I'll look into it further this weekend.

-Adrian

Scott Gray wrote:
Just because our test tools require container loading there is no reason why we couldn't run tests that don't require containers and use the junit ant task to run them during the test build:
http://junit.sourceforge.net/doc/faq/faq.htm#running_5
http://ant.apache.org/manual/OptionalTasks/junit.html

That reminds me, we need to upgrade to the latest version of JUnit, I'll take care of it this weekend.

Regards
Scott

On 20/11/2009, at 10:00 AM, Adrian Crum wrote:

I guess I was being myopic. Adam mentioned having to load the containers, and he's right - most component-level tests would require loading OFBiz in order for them to work. I was thinking only of the framework/base component - where you could run unit tests on the various classes found there. That wouldn't require container loading (I think).

Maybe it's too much of a bother. *shrug*

-Adrian


Scott Gray wrote:
You can run a single test suite using the main build file:
ant run-single-test-suite -Dtest.component=accounting -Dtest.suiteName=accountingtests it doesn't depend on the build target for some reason though but that could easily be changed.
Is this what you meant or something different?
Regards
Scott
On 20/11/2009, at 9:20 AM, Adrian Crum wrote:
What I had in mind was something like a run-tests ant target in the component's build.xml file. The run-tests target would depend on the build target.

That would make code testing really easy and convenient: modify code, run-tests, modify code some more, run-tests...

-Adrian

Scott Gray wrote:
On 20/11/2009, at 4:43 AM, Adrian Crum wrote:
I would like to build out the unit tests in the framework/base component, but I still need help getting that component's build.xml file to run tests.
Sorry I meant to look into it when you first raised that thread, I'll dig it up and see if I can help.
Regards
Scott

Reply via email to