wow! one of the first seleniumconf talks I could understand, most of the talks I find way over my head and talking about something so complicated I would never ever use.
try this one, ua-cam.com/video/rvcMIYy47xw/v-deo.html; same presenter, but it goes into details. The whole talk is essentially about a single slide from this one talk.
Yep, utility scripts to create test data can be quite valuable. Automation isn't always about the test/check itself, their are other opportunities to leverage your tool to help you do your job.
wow! one of the first seleniumconf talks I could understand, most of the talks I find way over my head and talking about something so complicated I would never ever use.
try this one, ua-cam.com/video/rvcMIYy47xw/v-deo.html; same presenter, but it goes into details. The whole talk is essentially about a single slide from this one talk.
Great talk on automation Richard!
Yep, utility scripts to create test data can be quite valuable. Automation isn't always about the test/check itself, their are other opportunities to leverage your tool to help you do your job.
Great talk indeed, so insightful
Great point on testability !
there are still valid reasons to check if an element disappeared from the page, though
In the stack of UI -> JS -> API ->APP -> DB - what is APP? the service? What testing JS mean here?
Good one
Haha yep, big consultancies are more like tool agencies or Dell for tools.