uTest Adds Real-Time Coverage Reports and Improved Tester Environment Tracking

Newest Version of Software Testing Platform Provides Customers with Improved QA Management Tools
Boston, MA
Nov 23 2009

uTest, the world’s largest software testing marketplace, today launched version 2.8 of its platform. This latest version includes a revamped user interface (UI), real-time testing coverage reports, and improved tester environment tracking. In addition, the platform design has been dramatically updated to match the uTest website, software testing blog and tester forums.

“Real-time information and structured data are critical to executing an efficient testing project, as the process often involves numerous teams, multiple projects and frequent analyses,” said Doron Reuveni, uTest CEO. “This new version of the uTest platform makes it faster and easier to get the detailed information our customers need when they need it.”

Real-Time Coverage Reports
uTest provides its customers with a testing coverage report at the conclusion of each project. The coverage report provides the customers with a complete record of all hardware and software environments that were tested, including handsets, OS, browsers, locations and languages.

Today, all of this detailed information is available in real time. Customers can now access these records while the project is still running. This gives customers a real-time snapshot of what has been tested and what still needs to be tested before the project is complete. Testing managers and uTest now have the information they need to redirect testers to cover elements that may need further validation.

More Structured Tester Data Per Bug
uTest also introduced a more precise way for testers to include their device details (OS, browser, firewall, anti-virus, mobile handset, etc.) with each reported bug. Leveraging uTest’s tester re-profiling earlier this year, the platform now stores a very detailed description of each tester’s individual testing environments, including all relevant software and hardware.

Now, when a tester reports a bug, they will be presented with a list of the testing environment information from their device profile. Instead of manually describing their environment in each bug report, testers can now choose which device was used to detect each defect. Bug reporting will be quicker, simpler, and more accurate; and the resulting bug data will be more structured and easier for customers to analyze.