From my perspective, E2E testing with Masquerade can be fully separated from the actual Jmix applications.
Considering SCS architecture, with multiple independent apps communicating with each other, it seems unnecessary to create E2E tests inside each application. Instead, why not have a dedicated lightweight E2E project?
Hi!
Thanks for the idea.
Creating such a template is not at all necessary. As you rightly noted, testing with Masquerade can be completely separated from the Jmix application.
The resulting template will be no different from a standard empty Java application template based on Gradle. The only difference will be the presence of a Masquerade dependency in the build.gradle file. You can create the same template right in your IDE.
I created an issue to mention this way in the documentation: Add a mention of the possibility of using the Masquerade separately · Issue #1085 · jmix-framework/jmix-docs · GitHub
Best regards,
Dmitriy