Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
by: Jim Holmes Selenium is a wonderful tool for automating acceptance and functional tests; however, real-world implementations bring a lot of pain. I suffered all that pain, and more, as I piloted an effort that started out with Selenium IDE, moved through RC, and ended up with WebDriver. This talk covers things like setting up baseline data, creating backing test frameworks, dealing with brittle tests, and figuring out how to appropriately manage all those incredibly slow Selenium tests so that you actually get effective, useful testing in. Learn from my pain (and successes!) so that you don’t have to suffer it in your own projects! Help us caption & translate this video! http://amara.org/v/GZC4/
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In the presentation "Surviving Growing from Zero to 15,000 Selenium Tests" by Jim Holmes, the speaker shares his journey of implementing Selenium for automated testing in an organization that originally did not value automation. The talk captures the progression from using Selenium IDE for initial tests to eventually scaling to 9,000 tests and dealing with the challenges that arose during this growth. Key points discussed include: - **Initial Adoption**: Jim describes starting with Selenium IDE to establish a proof of concept with 100 tests incorporated into the build process, which demonstrated the value of automation. - **Scaling Tests**: As the number of tests grew, they transitioned to Selenium WebDriver, allowing them to eliminate issues related to Selenium RC and improve test reliability. - **Challenges with Test Execution**: With 9,000 tests taking 16 hours to run, the feedback cycle was too lengthy, prompting the need for a more efficient solution. - **Test Granularity**: Jim discusses the importance of breaking tests into smaller, critical pieces to allow for faster execution and feedback. - **Infrastructure and Parallel Execution**: He emphasizes the need for proper infrastructure to run tests in parallel with tools such as Selenium Grid, highlighting how early scaling and distribution of tests can prevent bottlenecks. - **Treating Test Code as Production Code**: The speaker encourages treating test code with the same respect as production code, advocating for regular refactoring and maintenance to avoid brittleness in tests. - **Collaboration with UI Developers**: Jim underscores the value of communication with UI developers to improve testability and streamline the testing process. - **Cultural Shift Towards Automation**: The significance of fostering a culture that values testing and automation is also noted, as this can lead to more substantial organizational support for testing efforts. In conclusion, Holmes asserts that successful testing is not just about the technology but the people involved. He encourages building alliances within the organization and maintaining a focus on providing value through effective testing practices. By tackling infrastructure challenges early, treating test code seriously, and ensuring efficient feedback loops, teams can successfully implement and scale their Selenium testing efforts.
Suggest modifications
Cancel
