Selenium webdriver issue report mapped to RIMGEA

In this post I will map instructions how to report selenium webdriver issue to RIMGEA acronym. Those instructions should be used in your project.

Selenium webdriver, also known as Selenium 2.0, introduced webdriver API that made driving a browser natively locally or remotely more transparent. As I was using selenium behind clients corporate firewall, I thought that I found an webdriver issue. As I finished AST Bug Advocacy  course, I used knowledge and craft learned and gained at that course to report an issue.

Selenium project has rules how to report an webdriver issue. In that way, they get better community bug reports. By following those instructions, we are using A from RIMGEA acronym, and that stands for Articulate. Bug report will be articulated by following those instructions.

In order to be sure that this is really webdriver issue, user should first search project frequently asked questions. This is to filter out wrong webdriver usage and configuration issues.

You need to describe the issue as accurate as possible by answering following questions:

If you think that bug reporting process in your company or project is not satisfactory, I suggest that you start with selenium webdriver template and tailor it to your project needs.

Labels: ,