Full Stack Development with JHipster

Continuous integration

Having automated testing ensures that we are creating bug-free code, and also ensures that there are no regressions introduced from new code. JHipster helps to an extent, by creating unit and integration tests for the generated code, but in real use cases, it won't be sufficient. We would have to add server-side unit tests for the business logic that we introduce and integration tests for new APIs we add. You will also have to add more unit tests for business logic handled on the client side and e2e tests, as JHipster only generates a few sample tests for you and doesn't know anything about your business logic.

The more tests you have, more confident you will be changing code, with fewer chances of regression.

Testing ...