E2E testing strategy

[tadayosi]

One of the key things that were missing in the original Hawtio project was an E2E test suite; without E2E testing, we were unable to perform automated quality assurance on each new version release. We should ensure that this does not happen in Hawtio.next. Hawtio.next development should take E2E testing into account well into the early stages of the project.

The E2E testing strategy I'm considering at this time is as follows:

• E2E tests with runtimes to be run at hawtio and hawtio-online projects
  • hawtio - E2E tests for Spring Boot and Quarkus standalone
  • hawtio-online - E2E tests on Kubernetes and OpenShift (with microshift-action or a self-hosted runner)
• Component-level UI testing can be done at hawtio-next project
  • Leverage React Testing Library

Relating issue:

• Add E2E tests hawtio#2782

[tadayosi]

cc @jsolovjo @Croway

[tadayosi]

We can go with the testing strategy I outlined in the issue description. Let's close this as completed.