That's a good approach if you want to explicit...

2011-09-05T18:56:24.116+01:00

That's a good approach if you want to explicitly associate a class with the Junit class (or classes) that test it.

Alternatively, you can enable the "Run JUnits Automatically" option in the Sureassert UC Preferences. That monitors and runs all the JUnits in your projects automatically and reports errors/failures as Eclipse problems.

Either way, after the initial run it'll only run those tests affected by any changes you make (either to the test code or the production code it's testing), and you'll get the continuous coverage reporting.

If you go for the auto-run approach you'll probably want to tell Sureassert not to run some test classes (e.g. integration tests and slow ones) by annotating them with @NoAutoRun.

Comments on Captain Debug's Blog: Integrating SureAssert with Existing Projects

That's a good approach if you want to explicit...