Selenium (Se) Automation Gotchas
This session is for you if you experience any/some/all of the following:
- * Is your love for Selenium (Se) fading, because it is not as cool as it seemed during your days of dating it?
- * I have too many browsers and its versions to test my app against. Se just doesn't fit the bill.
- * The Se tests are damn slow.
- * The Se tests breaks more and more as the test suite grows.
- * The Se tests are simply unmaintainable. As the test suite grows, I fail to understand what's happenning.
- * Debugging Se tests are hard.
- * My Se test suite bacomes a beast eventually consuming all the resources of the machine it runs on.
Come join me as I share my experience encountering these and how I managed to maintain my love for Se. Let's have fun learning to love Selenium :)
Outline/structure of the Session
I'd run through my presentation, litterred with:
- Code Samples for good and bad code
- Q and A
- The attendees get to learn how not to write Se tests
- The attendees get to learn some best good practices on how to organize and write Se tests
Automation Test Engineers, Developers, Test Managers, Testing Leaders
schedule Submitted 3 years ago
People who liked this proposal, also liked:
Selenium DeTox for Achieving the Right Testing PyramidNaresh Jain
schedule 3 years agoSold Out!
Our project was a classic example of Selenium gone wild! As our team embraced the test automation journey, we went crazy and implemented tons of Selenium tests, one for every permutation possible. Soon we realized our feedback cycles were delayed. Our builds were taking hours instead of minutes. And we had a set of complex, fragile tests, which resulted in a lot of false-negative scenarios and finger pointing.
At this point, our team had realized that this is not the path forward. We decided to seriously look at our Selenium tests. We pretty much moved 80% of our Se tests to lower-layers (non-GUI based) tests. And now we have the right testing pyramid on our project.
Join us, as we explain our journey (strategy, techniques, tools, mindset-change and approaches we took) through this transition.
Embrace and Extend: How the Selenium Project Convinced the World's Largest Closed-Source Company to ParticipateJim Evans
schedule 3 years agoSold Out!
Microsoft. Just the name of the company alone can send some open-source software activists into fits of apoplexy. From the days when executives of the company compared open-source software to "a virus", the company has been seen as incredibly hostile to open-source software. It is surprising how much has changed over the years.
This is the story of how the Selenium project has managed its relationship with the software company, from the initial, tentative, often contentious and borderline hostile reaching out, to today's open engagement. The story is told through the prism of the Internet Explorer Driver project, with slight digressions to the .NET bindings and other Microsoft technology stacks. The journey is funny, sometimes frustrating, but always entertaining, and there may be a surprise announcement or two.
Testing of Responsive Web Applications using Appium and WebDriver API
All the modern web applications uses HTML5 and RWD (Responsive Web Design) to have an optimal viewing experience across a wide range of devices (from mobile phones to desktop computer monitors). Automating these applications and running the scripts on different devices is a bigger challenge.
How Appium and Selenium WebDriver API can be used to automate these applications and can also address all the challenges like:
1. Running the Webdriver scripts on iOS Safari and Android Chrome with minimal changes to the scripts.
2. Working with the Responsive web elements and validating their size and layout on different devices and viewports.
3. Automating complex gestures like Swipe, Tap, Pull to refresh etc.
4. Working with HTML5 based geo-locations and simulating the Mobile network bandwidth and latency using Browsermob