3 ms·
A core issue is the use of Record/Playback approach... something that Selenium itself has dropped long ago (Selenium IDE is dead, people, DEAD). In my experien
by p_l 10y ago
A core issue is the use of Record/Playback approach... something that Selenium itself has dropped long ago (Selenium IDE is dead, people, DEAD).
In my experience, once you stop trying to record clicks, often on elements that will dynamically change outside of your control, and instead use proper coded tests for locating UI elements like Selenium 2+ gives you, it's much easier to have both tests that don't break and tests that are easy to maintain.
- Zardoz84 10y agoWe had recorded/playback automated test for our main product that we converted to Java code and try to improve it... It's a nightmare.
- dokko1230 10y agoI agree that Selenium IDE has been long retired. To put into perspective, active development started in mid 2000s (2006 or 2007). If you look at the commit history on github, they only have a few commits sparkled in between months. But the focus of the academic journal (not the blog) was more of a focus on general record/playback testing tools, not just Selenium IDE.
- holtalanm 10y agoLast I knew, the code generated from Microsoft's CodedUI was absolute garbage. As an example.
- RandomBookmarks 10y agoThe thing is, "programming" tests might be the most robust solution if you know how to do it - but it also can be a waste of developer time. In the end, you spend your time on debugging the tests itself... In my experience, record and playback can work well. Especially visual, screenshot-based solutions like Sikuli or Kantu are actually more stable then most developers think. And the beauty of them is that they can also be used by non-developers, i. e. "manual testers", so the developers can actually work on the main product, not the test suite.
- dokko1230 10y agothose are some good resources. I didn't even know they existed.
- holtalanm 10y agoSikuli is great. Especially for automating non-web applications. I specifically remember a project I had where we automated an entire test suite using Sikuli on an SAP frontend. Kinda led me to create https://sourceforge.net/projects/sikuli4net/ https://sourceforge.net/projects/sikuli4net/ Sikuli4net is pretty much a dead project now due to me having absolutely no time to devote to it though. :(
- HashHishBang 10y agoThat kind of attitude is why my entire career path exists. QA Automation is something that I'm constantly surprised people don't know exists. Product devs resent writing tests so we are the ones who do that exclusively. As a counter to your experience I've spent a great amount of time stamping out issues with record-and-playback tests. They're a passable stop-gap if you desperately need testing and, for whatever reason, haven't written any. Sikuli is possibly worse, though it's been a few years since we last evaluated it and quickly decided against using it in any serious capacity. Using manual testers as discount automation testers is a waste of everyone's time. They're the true experts in actual use of the product. I've seen them find more issues that from a code perspective shouldn't really be possible that it's given me an implicit trust and respect of their abilities. If someone wants automated testing it's another thing they're going to have to spend money on. Doing it half-assed is more than likely going to do more harm than good.
- defied 10y agoI work for testingbot.com where we still have a significant part of our customers who use Selenium IDE scripts. The biggest reason for this is because they don't have the time or knowledge to re-write their scripts to use WebDriver. So even though Selenium has dropped support for IDE a long time ago, it's still being used by testers.