I've used selenium pretty extensively since 2007. There are a lot of good examples out there, the docs are good, and its written in a very extensible way, so I've always been able to find a way to accomplish what I'm trying to do. (anything you can do in javascript!)
Ways I've used it:
1. create basic smoke tests that test the happy path of an app, to be run after a new deployment
2. use the Selenium IDE firefox plugin to record a 'how to recreate a bug' scenario, and attach it to a bug report, greatly reducing the amount of time to document and explain the steps it takes to get a bug to happen.
3. when integrated into the app, with some customizations, allow a QA user to dynamically choose elements to feed the selenium test (2 adult, 1 child, ord-sfo, round trip, with refund)
4. to fill in forms I don't want to fill in again (chili's and home depot receipt surveys)
5. Setting up accounts, re-initializing my stupid vonage motorola router that loses its settings if the power goes out
Selenium is great, and has gotten people thinking about how to test the app and drive it the way that the user experiences it.
There are certainly some draw-backs, and other tools that should be explored, but I think Selenium is part of a 'balanced testing diet'.
Ways I've used it: 1. create basic smoke tests that test the happy path of an app, to be run after a new deployment
2. use the Selenium IDE firefox plugin to record a 'how to recreate a bug' scenario, and attach it to a bug report, greatly reducing the amount of time to document and explain the steps it takes to get a bug to happen.
3. when integrated into the app, with some customizations, allow a QA user to dynamically choose elements to feed the selenium test (2 adult, 1 child, ord-sfo, round trip, with refund)
4. to fill in forms I don't want to fill in again (chili's and home depot receipt surveys)
5. Setting up accounts, re-initializing my stupid vonage motorola router that loses its settings if the power goes out
Selenium is great, and has gotten people thinking about how to test the app and drive it the way that the user experiences it.
There are certainly some draw-backs, and other tools that should be explored, but I think Selenium is part of a 'balanced testing diet'.