The JHipster team always tries to generate code that performs well. For the backend code you can decide to use Gatling to generate perfomance tests. Most of the times Matt Raible is doing a lighthouse test for each release manually, but there is no automated regression testing for a generated application.

This is part 2 of Creating a JHipster Playwright Blueprint.

JHipster offers good support for doing end-2-end tests. Recently Cypress has been added as the default option and Protractor has been deprecated.

Since JHipster v7.0.0-beta.1 the login page is not rendered in a modal dialog anymore. Therefore this post applies only yo JHipster 6.x!

When it comes to testing JHipster provides a wide range of tests out of the box. Recently I found Greenmail. Greenmail is a java library to test sending and receiving of emails from Java. This is quite useful during to development to test sending of emails (e.g. to check if all is configured correctly or if the responsiveness is fine in different email clients). Furthermore you can use greenmail in unit or integration tests which makes the setup of such tests easier as the sending of emails must…

As you might noticed, I really like JHipster and Testcontainers. Right now, when you create a JHipster application and choose e.g. PostgreSQL as your database the integration tests (annotated with @SpringBootTest) are still using an H2 in-memory database. This helps to make the first time experience for our users quite smooth as they don’t need docker for example. When you are planning to use some specific functions of your choosen database H2 is not the right choise anymore. In fact JHipster…