As for the Graphical User Interface, Vester uses the egui GUI library for Rust.
With the usage of GitHub Actions when a pull request is opened towards the vester_visual_testing branch, the HTTP Request to Vester on pull_request for visual testing will start, that will send an HTTP request to the server hosting the Vester client (the HTTP comms are managed by a warp client), which will proceed to download the merging repository, compile the binaries, execute the egui demo app and visually test it, then send the results back, ending the Action. In case the test was successful it would be safe to assume that the merging branch's commits do not alter the visuals of the resulting application, therefore we can proceed to merge it and close the pull request. An example of an automated call to Vester by a GitHub Action triggered by a pull request can be found here.
And it can also visually test web pages!Coming next: an API that enables integrations with back-end/front-end testing suites like Bun.