search

nengo / nengo-1.4

Create and run detailed neural simulations
http://www.nengo.ai/nengo-1.4
96 stars 22 forks source link

Migrate to JUnit4 #363

Open tbekolay opened 11 years ago

tbekolay commented 11 years ago

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.

codemercenary commented 11 years ago

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 commented 11 years ago

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.

tbekolay commented 11 years ago

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