Test Run Features

Test Run helps you and your team create, manage, and execute test plans.

Faster, Better Test Planning

First and foremost, Test Run helps you and your team create, manage, and execute test plans.

Manage Test Cases Easily

Test Run makes it easy to create new tests by eliminating a lot of the complexity that has slowly been added to so many other tools. Test Run differentiates itself by keeping its test cases simply structured and by focusing test engineers on the most important parts of the test case: the instructions on how properly execute the test.

Create Test Plans Quickly

When it comes time to build a test plan, Test Run allows you to quickly create a plan comprising all the test cases with a given keyword or tag. Just enter in the tags and keywords relevant to your testing goals and Test Run will generate a test plan composed of the test cases with the tags you entered.

Quickly View Passed, Failed and Blocked Test Cases

Once testing begins perhaps one of the most important tasks performed in monitoring the progress of the testing process is the inspection of test cases and their status. Blocked and failed test cases may help identify areas of functionality with high degrees of risk associated with them, while test cases with other statuses can help you to hone your process, more evenly distribute the testing load across your team and help your product converge on a high degree of quality more quickly.

Increased Visibility and Transparency

Test Run is a tool built for managers first and engineers second. It is tool built and designed by a project manager to help other project managers stay abreast as to the progress their QA team is making.

Testing Dashboard

When first logging into Test Run, users are presented with a dashboard that gives everyone an instant snapshot of every test plan being actively worked on. At a glance users can monitor the health of the projects they are working on and track a project throughout its life cycle.

Detailed Reports

Managers are given a number of reports to choose from to help them monitor their projects and system. The “Quality Convergence” report helps to illustrate how quickly a test plan is approaching completeness, while a “Load Balancing” report allows project managers to diagnose the work load across their team and to distribute accordingly. Choose from a number of different reports depending upon your needs.

Test Case History

Test Run is not limited to giving stake holders a picture of the present, but it also maintains a historical record of test execution over time. It then gives you access to that test case history at the click of button, thus allowing you to make adjustments to your process and test plans in order to ensure a higher degree of quality the next time the plan is executed.

Optimized Process for Agile Development

Use Tags, Not Complex Categories

Tags are a simple and powerful concept that allows Test Run to accommodate just about anyone's process and schema. Tags are "labels" or "keywords" that one associates with test cases to help categorize them. Because tags are unstructured, they can conform to any pattern you wish. Tags can be used to label test cases with a Feature Request ID, or a bug number. Bottom line, tags give you all the flexibility you need with out making the user interface or data entry process overly complex.

Integrate with Existing Issue Trackers

The last thing we at Test Run want if for you to have to up root your entire toolset just to use our software. Instead, we integrate seamlessly with Jira and Lighthouse, two very popular bug and issue tracking systems. With this integration QA engineers can easily report new bugs from directly within Test Run while they are executing a plan.

Integrate With Your Bug-Tracking System

A critical compliment to Test Run is your bug tracking system that allows you to instruct engineers to fix defects. When a test case is marked as "failed," Test Run will prompt the users for the resulting bug ID. That Bug ID is then permanently associated with the test case and is used in subsequent reports and test case histories. When the bug is resolved, one can later mark the bug in Test Run as fixed.

See what's coming in future versions of Test Run.