Java EE

In which situations should we use Cypress or Robot Framework? Are both good choices to get tenured manual testers into the practice of automating their work for tests of APIs and functional tests of web applications? Cypress looks great for functional testing of web applications and Robot Framework looks great for everything else.

Background: We have over a thousand functional test cases for our web applications being executed manually by a QA team. Our front ends interface with APIs written in Java with various frameworks over the years (e.g. Spring, Spring Boot, Java EE). I think our testers could learn enough of the basic coding in JS, Java, and Python required to automate most of those cases.

Hi, I'm working on dockerizing a heavy Java EE application where the process of installation requires a complex process maintained by a Gradle project we've developed to install, configure and customize specific jar files to generate a runnable server application at the end for the user. I'm new to Docker. As I said, the problem is that we have got a long process to install the app. The first alternative pop into my head is to put the installer Gradle project in the docker image and manage stateful data using the writable layer (in this case, I need to add Gradle too and the writable layer will be too heavy). Any advice! Thank you

Moving from a classic monolithic Java EE application on-premise to a cloud application based on microservices. What is the easier framework to learn/to move on? is Quarkus enough mature for production? Is the performance of Quarkus in production the same as the benchmarks suggest?