Automated frontend perfomance test with lighthouse for JHipster

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. When choosing Cypress as end-2-end testing framework one could use cypress-audit to automate the manual lighthouse test. This will be beneficial to the JHipster development to identify regressions and for JHipster users as they can test the frontend perfomance more easily. [Read More]

Creating a JHipster Playwright Blueprint - Part 2

Note: This is part 2 of Creating a JHipster Playwright Blueprint. When creating a JHipster blueprint you usually start with an application and modify it to your needs. Afterwards you can start to modify existing templates or creating new ones if needed. As JHipster offers a lot of different options you might need to modify multiple applications in order to get the templates right. In this post we will integrate Playwright into an existing JHipster application. [Read More]

Creating a JHipster Playwright Blueprint - Part 1

JHipster offers good support for doing end-2-end tests. Recently Cypress has been added as the default option and Protractor has been deprecated. While maintaining protractor tests for three frontend stacks (angular, react and vue) was not easy, we are very happy with what Cypress offers. The tests are much more stable and the developer experience is great. Nevertheless Cypress has some drawbacks as it focuses on doing one thing well. [Read More]

Replace the login modal with a separate login page

Note: 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! During my last talk about JHipster I was asked if it is possible to replace the modal login dialog with a dedicated login page. I remember doing that for the angular 1 frontend as it was possible to configure in the router if the content was rendered on a modal dialog or not. [Read More]

Using Greenmail to enhance JHipster Integration Tests

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 not be mocked. [Read More]

JHipster With Testcontainers

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. [Read More]