Analysis updated 2026-08-13 · repo last pushed 2015-03-24
Identify which Selenium commands are slowing down a long-running automated browser test suite.
Debug a specific test by enabling verbose output to see what commands are executing behind the scenes.
Optimize test suite performance by finding pages that load too slowly or interactions repeated unnecessarily.
| titusfortner/webdriver_statistics | 0xdevalias/huginn-chef | 100rabhg/masterdetailapp | |
|---|---|---|---|
| Language | Ruby | Ruby | Ruby |
| Last pushed | 2015-03-24 | 2014-09-30 | 2024-02-20 |
| Maintenance | Dormant | Dormant | Dormant |
| Setup difficulty | easy | hard | moderate |
| Complexity | 2/5 | 4/5 | 2/5 |
| Audience | developer | ops devops | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires an existing Selenium-based Ruby test suite to plug into, no standalone infrastructure needed.
WebdriverStatistics is a tool for teams that use Selenium to automate web browser testing. It tracks every command your test code sends to the browser, things like clicking buttons, loading pages, or typing text, and records how long each one takes. When a test finishes and the browser closes, it prints out a tidy summary of everything that happened. The tool works as a plug-in for existing Selenium-based test suites. Once it's added to a project, it quietly watches in the background, counting commands and measuring execution time from the moment the browser opens until the moment it closes. At the end of each test run, it prints a formatted report to standard output. If you need more detailed debugging information, you can flip on an environment variable to get extra insight into what's happening behind the scenes. This would be useful for quality assurance engineers, developers, or anyone running automated browser tests who wants to understand why their test suite is slow. For example, if a full test run takes 20 minutes, this tool can show you exactly which commands are eating up the most time, maybe a particular page takes too long to load, or a specific interaction is being repeated unnecessarily. That kind of visibility makes it much easier to optimize tests and fix bottlenecks. The README doesn't go into much detail about the format of the output or what specific metrics are included beyond counts and times. It's a fairly lightweight, focused tool that does one job: giving you visibility into what your Selenium tests are actually doing under the hood.
A lightweight Ruby plug-in for Selenium browser tests that tracks every command sent to the browser and prints a summary report showing how long each action took, helping teams find slow spots in their test suites.
Mainly Ruby. The stack also includes Ruby, Selenium.
Dormant — no commits in 2+ years (last push 2015-03-24).
The README does not specify a license, so usage terms are unknown.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.