test: wait for Vaadin after opening route

[javier-godoy]

I added getCommandExecutor().waitForVaadin() call to the @Before method immediately after navigating to the URL, so that the browser has fully initialized the Vaadin client-side engine before the test logic begins execution.

Previously, this setup was highly unstable. Because driver.get(url) only waits for the initial HTML to load, the test would often proceed to call RPC methods before the Vaadin Flow framework had finished initializing the view on the client side.

This resulted in frequent test failures with the following error:

"Could not find view. Check that the view contains @ClientCallable methods"

This error was misleading; the methods existed, but the UI has not been initialized yet.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud