Selenium in 2016: What Testers Need to Know About the Current State and Future of Selenium
Web is undergoing dramatic changes which continue to alter the way automated tests need to created and maintained.
Along the side lines, over the last year, we have also seen browser vendors placing a lot of emphasis on making web secure, stable, and power-efficient. And in that process, they have made it difficult for testers to bypass UI by restricting access through plugins and APIs.
With all these changes taking place, Selenium has become the default standard for web testing, as evidenced by a 300% increase in job postings over the past 3 years.
It has come a long way since its inception with Selenium IDE (Integrated Development Environment) and Selenium 1 (Selenium Remote Control). The future of Selenium looks different than it did a year back.
What does this means for testers and developers?
The question then arises is: what do all these trends mean for web testing and how can testers equip themselves to better handle these changes? Also, it is crucial to understand what the future of Selenium looks like.
I answered these questions — along with many others — I sat down with special guest, Dave Haeffner for a special webinar on January 27: Web Testing and Selenium – The Current State and Future Possibilities.
Dave is the author of Elemental Selenium and co-organizer of Selenium Hangout.
Some of the topics we touched upon during the webinar include:
- Web testing trends in 2016 and what they mean for Selenium
- How is Selenium accommodating to these trends?
- Traditional challenges associated with Selenium
- How to overcome these challenges while designing test cases
- What does the future of Selenium look like?