Optimize build/test execution time

[stephan-strate]

First of all: Thanks for your work. This extension is amazing :)

I would like to start a discussion about optimizing the execution time for testing and building the frontend application.
Problem: Having the backend and frontend application separately, each needing build time (including tests) of eg. 3 minutes. When using quinoa this build time increases to 6 minutes, because these processes are executed sequentially.

First idea: Wouldn't it be possible to execute backend and frontend tests in parallel?

What do you think? I am happy to help and contribute.

[ia3andy]

Hello @stephan-strate :)

Thanks for the great feedback. It makes me really happy to hear those!

First idea: Wouldn't it be possible to execute backend and frontend tests in parallel?

Something we could do: make it easy to call the webui tests from a specific Junit test, then, it's up to anyone to choose how they should be ran through JUnit (sequential or //).. It would also give a finer control over running those tests, we could even imagine allow to call different frontend test group from different junit methods (and have an environment/options to update the snapshots if used). Also, I think it makes sense to have those test closer to the Playwright E2E tests (if there are some).

Optimizing the build time

For this, I am not sure we can do anything as it is tied to the Quarkus build system. I am all hear for propositions thought..

Cheers,

[ia3andy]

Ok, I get your point, so yeah you could give a try to the maven multi-modules to get an idea of how significant changing this would be. I am quite skeptical on the gain, I am eager to have your results :)

[stephan-strate]

@ia3andy I ran into some problems executing my idea. As the whole execution is tied to the quarkus-maven-plugin, I can not put the frontend into a separat maven module. As far as I know maven multi-module project always have one module which bundles all the others and has the quarkus-maven-plugin installed. All others do just use jandex to index the CDI beans.

[ia3andy]

@aloubyansky might be able to help you..

[aloubyansky]

If the goal is only to run tests, you don't need to configure the quarkus-maven-plugin in a module unless there are source code generating extensions in the project. What you need is quarkus-junit5 in test scope.

[stephan-strate]

@aloubyansky quarkus-quinoa runs the frontend build and tests using a BuildStep. So as far as I understand, quarkus-junit5 won't do anything here.