[v2] end-to-end testing?

[tassa-yoniso-manasi-karoto]

I was looking for ways to test my app and GPT suggested E2E testing:

End-to-end (E2E) testing is a methodology that verifies the full workflow of an application from the user's perspective. It simulates real user interactions—from launching the app and navigating through its interface to triggering backend processes—and checks that every component, including the communication between the frontend and the Go backend via the Wails runtime, functions as expected. This type of testing ensures that all layers of the application work together seamlessly, providing a holistic validation of the system's behavior.

But after further consideration I realized I can't use the frontend's developement localhost address in a browser because it isn't connected to the backend functionality.

Come to think about it, using go-rod in dev builds to control the browser could be a basis for these tests, but go-rod need a WebSocket URL for chromium devtools, and I'm not sure if Edge Webview can provide one.

Any insights on this?

[gerbil]

I got this covered by starting backend with cypress as e2e testing tool running from edge browser.

[tassa-yoniso-manasi-karoto]

I got this covered by starting backend with cypress as e2e testing tool running from edge browser.

I hadn't heard about cypress, thanks. But this setup can't communicate with the go backend right?