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!

After the recent thunderstorm killed my old Fritz!Box we needed a new router. As I never used a lot of the features a Fritz!Box has to offer I looked for alternatives. Finding a router with integrated modem and phone functions reduces the amount of devices, In the end I needed to decide between the highend devices Fritz!Box 7590, TP-Link VR2800v and the entry level VR600v. I would have also considered the mid level VR900v but currently only the older revision v1 is available.

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…