Selenium provides this capability with a tool that records where you click on your website and then it records that as a macro which acts as an automated test.
However, the issues remain the same as with any other ABT test. An async element might take a while to load due to latency, and isn't there by the time your test says to click a button, or browsers were updated and now render your CSS just differently enough to break the test.
Perhaps part of the challenge is there are so many things that can change and break the tests outside of the actual code.
Comments
How can we solve that? Perhaps we need a automated browser testing that can be used by non-developers?
Selenium provides this capability with a tool that records where you click on your website and then it records that as a macro which acts as an automated test.
However, the issues remain the same as with any other ABT test. An async element might take a while to load due to latency, and isn't there by the time your test says to click a button, or browsers were updated and now render your CSS just differently enough to break the test.
Perhaps part of the challenge is there are so many things that can change and break the tests outside of the actual code.