01-11-2012 08:26 AM - edited 01-11-2012 08:27 AM
In one project we spawned a command shell programatically and ran NdTestRunner inside it, using the exit code to evaluate a binary success/failure for the test run as a whole, and then wrapped that in a Maven plugin which ran during the test phase of our build. I hope there's a better way to run tests programatically, but have not been able to find one. It was quite cumbersome to get the classpath to a working state.
01-13-2012 05:51 AM
Thanks for the reply
1.)Can you share some piece of code where it calls NDTestRunner from shell script?
2.)Also, it would be helpful if you elaborate on CLASSPATH setting to a working state.
a)Do we have to point Repository or workspace?
b)If so, which directory we have to point out in our BUILD scripts?
01-13-2012 09:19 AM
1) Sorry no, it's part of an NDA-bound closed source project that I don't work for any more.
2) I'm not the one that actually programmed it, but I think after getting fed up with guessing, the guy who did it just went for calling the setenv.bat from the shell, and then adding more classes programatically or through maven dependencies from our own custom projects (domain model etc.) until it worked. I remember one strange thing he had to do was to reverse the order of the generated classpath.
He also generated the test configuration xml files fed to the command line test runner through introspection of the repository using an appropriate BA API. He accessed an automatically checked out/updated workspace, using another custom made maven plugin.