JHipster comes with an extensive set of tests, and each generated application has:
We have two goals in generating those tests:
mvn clean testand
grunt testafter generating your application is a good way of knowing if everything is fine. You are then free to ignore those tests if you think that testing is a waste of time!
All those tests will be generated in the standard Maven
Integration tests are done with the Spring Test Context framework, and are located in the
src/test/java folder. JHipster will launch a specific Spring test context, which will be re-used along all tests, as:
This Spring test context will use a specific test database to execute its tests:
Those tests can be run directly in your IDE, by right-clicking on each test class, or by running
mvn clean test (or
./gradlew test if you run Gradle).
Limitations: if the generated entities have validation enabled, JHipster is not enable to generate the correct values depending on the validation rules. Those rules can be so complex, for example if a Regex pattern is used, that this just not possible. In this case, the tests will fail validation, and the default values used in the test will need to changed manually, so they can pass the validation rules.
Those tests will mock up the access to the application's REST endpoints, so you can test your UI layer without having to launch the Java back-end.
Those tests can be run using
grunt test (or
gulp test if you use Gulp.js).
Performance tests are done with Gatling, and are located in the
src/test/gatling folder. They are generated for each entity, and allows to test each of them with a lot of concurrent user requests.
Gatling tests can be run with Maven, by running
mvn gatling:execute. If you have several tests, JHipster will ask which test should be run.
Warning! At the moment, those tests do not take into account the validation rules you may have enforced on your entities. You will anyway need to change those tests, according to your business rules, so here are few tips to improve your tests:
Administration > Logsscreen, and put
debugmode. You will see the validation errors, for example.
console log: you will be able to see the REST requests with all their parameters, including the HTTP headers.
Gherkin features will have to be written in your