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!