News for hackers. Stuff that matters.
Re:Why Recorded/Playback Tests in Selenium Break by shouldbworking on Tuesday April 18, 2017 @05:57AM (#14137510)
I find automated UI tests to be a massive waste of time in every shop I've worked that used them.

Just smoke test that all the inputs do something and unit test anything else you care about.

UI testing is an antipattern

Re:Why Recorded/Playback Tests in Selenium Break by ozim on Tuesday April 18, 2017 @08:09AM (#14138140)
I am on the same page, I used page objects and was adding Ids to everything with retry couple times before failing (state of art interface automation?) but tests were flaky anyway so I gave up on that. Just too much hassle for little or no return if interface changes. Let alone testing multiple browsers...
Re:Why Recorded/Playback Tests in Selenium Break by saimiam on Tuesday April 18, 2017 @08:20AM (#14138199)
I was facing exactly the same issues with my automated tests so I wrote a wrapper to help me completely avoid writing page objects.

https://github.com/saiscode/8tomation

With this, your basic cucumber .feature file (with minor restrictions) can be executed without needing page objects. Take a look if you have a second...