@jeder when i was working as a tester in college i had to write selenium tests for the website and holy shit i could not get away from flakyness cause the loading was just so bad it would find new ways to fail all the time
@jeder imo automated UI tests can be good (idk abt cypress so im just gunna talk abt selenium since ive used that) if the devs are forced to improve the flakiness rather than make whoever writes the tests try and work around that.
@emilis cypress is pretty much just a javascript thing that instructs what browser clicks/does so it's pretty close to what user is doing, but yeah it can get flakey most of our work is manual anyway, some testers sometimes write cypress tests but it's not the primary focus
@jeder ah okay, selenium is much the same in functionality but it's got integrations in other languages for the driver (I've written it in C# at said job and in rust for some browser automation tool for myself last year)
@emilis@jeder perhaps, i'm just having situations at work where if the backend takes a second longer than usual to respond the test will fail because the page won't load in time (i'm additionally cursed with having to deal with a js framework that does SPA by loading html from the server and the testing framework does not know to wait for the loading to finish)