...
Warning: if you get the class name wrong, it doesn't complain to you. It just iterates its way through all the potential testable modules, saying "No tests to run for ...". Not very helpful for finding out you had a typographical error in the class name.
Running Outside Tests
Tests may exist that cannot be included in the Daffodil repo, usually because of size or privacy concerns. However, it is still desirable to build and run the tests as if they were part of the normal sbt build/test process. The Daffodil build system provides a way to do this, using the daffodil-extra directory. First, create a directory containing tests using the SBT Directory Structure (you really only need src/test, and you do not need to create any sbt definition files, like build.sbt). Once this is created, add a symlink from the daffodil-extra directory to the root of your test directory:
| Code Block |
|---|
$ cd daffodil-extra
$ ln -s /path/to/root/dir/of/custom-tests |
With sbt restarted, the custom-tests directory will appear as a normal daffodil subproject, with the tests run as if they were part of the normal Daffodil test suite. The directory name is used as the sub-project name, so you can use standard sbt commands to run only the tests in that project, for example:
| Code Block |
|---|
sbt custom-tests/test |