Enhancement: any way to run tests faster?

[t-jones]

I've been using testNG for a couple years and enjoy its flexibility. The only gripe I have is run speed compared to the junit plugin. I recently worked on a project which was running junit, and for a simple test class of a dozen or so tests, run speed was about 1/10th what it is in testng. I assume this is b/c each testng run launches a java process; according to the stats in the console after a run, the internal execution is pretty fast (~200ms) compared to the run-time in the plugin panel (~1000ms). This may not feel like much, but when you are executing tests several times a minute while working on bug fixes and the like, it starts to feel like you are always waiting on the tests to finish.

Does this resonate at all? Any way to run them faster I just don't know about? Any thoughts on other ideas? Happy to do some hacking myself.

[cbeust]

Both TestNG and JUnit launch a remote Java process to run the tests, it's the only way.

The graphic aspect used to slow down the tests considerably because the live update of the tree was being slowed down on the event dispatch thread, so I disabled this live update (the only live update you see now is the red/green gauge). If you want to experiment, how about starting with disabling the gauge and see if it makes any difference?

[missedone]

any suggestion or pull request are welcome