Implement UI testing

[EddeCCC]

There was already a bit of preparatory work for the UI testing in the former Config Server: inspectIT/inspectit-ocelot#1458

The goal is automated click tests for:

• Verification of basic functionality
• Performance recording

On the one hand, tools such as https://playwright.dev/ or https://www.selenium.dev/ are to be evaluated for their suitability.

Verification of basic functionality

A default use case mentioned in the workshop for potential automation is e.g:

• Create configuration
• Edit configuration
• Delete configuration

Attention! Don't just scan happy paths! Edge cases are particularly important! What happens if something invalid is entered / arrives / is created? What if the data type does not match? What if a date is non-sense?

Performance recording

The following applies: The benchmark of the current (as of March 2025) ocelot version applies as a standard.
Other valid Tresholds:

• Web vital Treshold
• Simultaneous connection of <= 200 agents must be guaranteed