Re:Launch HN: GPT Driver (YC S21) – End-to-end app testing i...
by usernameis42 on Wednesday October 23, 2024 @11:26AM
(#41926019)
There is great approach based on test-id strategy, basically it's a requirement for the frontend teams to cover all interactive elements with test-id's.
It allows to make tests less flaky and writing them is increasing dramatically, also works with mobile as well, usually elements for the main flows doesn't change that often, you'll still need to update them.
I did stable mobile UI tests with this approach as well, worked well
Re:Launch HN: GPT Driver (YC S21) – End-to-end app testing i...
by digging on Wednesday October 23, 2024 @10:53AM
(#41925665)
> Versions change: UI elements move, change their title slightly
Not randomly, I'd hope. I think you may be misunderstanding what deterministic means - or I am.
Re:Launch HN: GPT Driver (YC S21) – End-to-end app testing i...
by minhaz23 on Wednesday October 23, 2024 @12:16PM
(#41926517)
Ever worked with extjs? :/
Re:Launch HN: GPT Driver (YC S21) – End-to-end app testing i...
by MattDaEskimo on Wednesday October 23, 2024 @11:02AM
(#41925767)
It's crazy to have people so out of their league try to argue against well established meanings.
A testing framework requires determinism. If something changes the team should know and adjust.
AI could play a bit in easing this adjustment and tests but it's not a driver in these tests.
And then there are truly dynamic apps like games or simulators. There may be no accessibility info to deterministically code to.