The key problem to entry is simply getting people to record the actions and the issues they are reporting. I often find trying to reproduce the problem on complex software can take around 30 minutes. With a simple recording using selenium IDE, you can easily replay and help isolate the problem. Not all of our clients are onsite, as such this takes the developer longer to identify or clarify what the issue is. Often tickets provide many ambiguous interpretations and the mean time to resolving an issue would be reduced.
By building a collection of these tests with any issues that do arise you will be building a larger collection of repeatable tests and the key to this is repeatability.
Some of there references I used can be found at:
- Selenium Tips: Improving your waiting skills
- Selenium Tips: CSS Selectors in Selenium Demystified
- Selenium Tips: Finding elements by their inner text using :contains, a CSS pseudo-class
- Selenium Commands & Locators Explained
- Why CSS Locators are the way to go vs XPath
- 5/19 Meetup Videos: How Mozilla and LinkedIn use Selenium
- Continuous Deployment—the video
- Parallel Automated Browser Testing in PHP using Selenium and Sauce OnDemand
- How Mozilla Uses Selenium