customization

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]

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]

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]