nengo-1.4 icon indicating copy to clipboard operation
nengo-1.4 copied to clipboard

Published 20 hours ago • verified publisher icon nengo

Migrate to JUnit4

Open tbekolay opened this issue 12 years ago • 3 comments

Right now all our tests are using old-style JUnit syntax. We should upgrade to JUnit4 and start writing tests with the simplified JUnit4 syntax.

It's not necessary to upgrade all our old tests to the new syntax, but it wouldn't take too long.

Another advantage of JUnit4 is the ability to run unit tests in parallel. Could speed up the build process a bit.

tbekolay avatar Dec 20 '12 15:12 tbekolay

All of the old tests have been converted to the new annotation-based syntax in this changeset.

See pull request #365 for the fix.

codemercenary avatar Dec 20 '12 17:12 codemercenary

My next step will be to remove the slower unit tests from typical testing, and include them as part of an integration test package. Can your CI server be altered to include the execution of integration tests? I find the easiest way to do this is either to specify an "integration-test" goal specifically, or to introduce another property that can be detected in the POM which turns on more tests.

codemercenary avatar Dec 21 '12 18:12 codemercenary

Yes, we can modify Jenkins to do this! Using @Categories or some such, I would think.

tbekolay avatar Dec 23 '12 20:12 tbekolay