This screencast shows how you, when you found a bug, can use Selenium to target that specific bug. Once the Selenium test is written, it can be run over and over again while trying to fix the bug – and be included in future test suites to make sure that the bug doesn't reappear.
In the example, there is also a variable "base path" that can be used for setting any sub folder of your Drupal installation – making the test run smooth even in non-standard installations.
If reporting bugs in module issue queues, many maintainers become happy if you attach well-made Selenium tests!
Modules:
Additional Resources: