...
- A config-test.properties file must exist for each type of loader that is configured to point to a database that contains no data (this is a destructive test). Each file is specified with a variation of "run.config". See the example below.
- the different properties files are configured with handlers that know how to deal with different formats once loaded.
- the various config sub-projects have config.properties files that can be used as a guide.
- They can all point to the same database for testing
- A server may or may not be running at the "base.url" specified in the "config-test.properties" files. If so, mojos will connect to the server, otherwise not.
- A "maven.home" property must be specified to bootstrap the process
- A run.config.umls property must ALSO be supplied for the mojo itself to access JPA services. Any of the test file should be fine.
Run using the "mojo" profile (this will run only mojo integration tests). For example (command line execution):
| Code Block |
|---|
cd integration-tests mvn -Pmojo install -DskipTests=false -Dmaven.home=c:/apache-maven-3.0.5 \ -Drun.config.rrf=c:/umlsserver/config/config-testrrf.properties \ -Drun.config.rf2=c:/umlsserver/config/config-testrf2.properties \ -Drun.config.claml=c:/umlsserver/config/config-testclaml.properties \ -Drun.config.owl=c:/umlsserver/config/config-testowl.properties \ -Drun.config.umls=c:/umlsserver/config/config-testrrf.properties |
Here is a sample Eclipse run configuration for the same test:
REST Integration Tests
...