-
Notifications
You must be signed in to change notification settings - Fork 16
Proof of concept for using unit test framework #12
Comments
In 3.3, build.gradle is now set up with support for ScalaUnit (commented out):
Uncommenting these lines will enable "./gradlew test" with ScalaUnit. I would like to replace some test cases with ScalaUnit, so multiple tests can be run in parallel and without restarting the whole JVM. Example from
This results in:
This could be done by rewriting config/src/main/scala/modbat/config/ConfigTest.scala as a ScalaUnit test in config/test/main/scala/modbat/config/ConfigTest.scala:
https://stackoverflow.com/questions/4183408/redirect-stdout-to-a-string-in-java
|
There is a better way to redirect stdOut and stdErr, as used by
"err" and "out" have to be PrintStreams that are set up for redirection. See At first, we probably want to use two In a next version, we could provide a front-end to tests that use |
We would like to use a unit test framework for most (all?) tests, to abolish our own test runner, and to allow parallel testing.
First, a proof of concept is needed that shows how two or three tests run inside such a framework and possibly interact because static fields are not reset.
This may in turn require changes in Modbat's configuration handling or even beyond.
The text was updated successfully, but these errors were encountered: