Happy Testers – ReQtest Requirements Implemented Fall 2016 – Spring 2017

Update for “Happy testers”.

One of our main objectives from the start has been “ease-of-use while being intuitive”. To do that, the tool we built had to support you rather than hinder your work, letting you focus on your core business.

In time the key focus was placed on testers and test managers, more specifically on:

Simplifying workflows to enable users to be more productive
Helping testers be more efficient while conducting tests in ReQtest, thus saving time
Gaining better insight into test data from which to draw conclusions

Our drive to make ‘Happy Testers’ has been realized thanks to your feedback, which helped us to come up with this list of features, all of which have been released in ReQtest.

Planning, tracking, and following up on tests:

Test report. A completely revamped test run page to which present clear results more clearly, alongside a test run progress chart, and the quantity of work remaining.
Share a test report with others. Easy sharing, simply email a test report with charts of your test run status to your test leader or manager.
Add new step in a test case by pressing Ctrl+Enter. This and other shortcuts will save time when writing test cases.
Keyboard shortcuts in checklists. Save time by using your keyboard to add, delete, and move rows in a checklist.
Test suite names in the test case list. Test suites are now listed by name instead of ID in the new test case list page.
Upgraded test suite list. Easily find the correct test suite in a long list by sorting and filtering the list of test suites.
New test suite page. Easy drag and drop to reorder test cases in the new test suite page.
Chart test results. Draw charts for test cases based on their execution results.

When executing tests:

See bugs reported from a test run. All bugs found in your test run are nicely presented on the test run page. The bug reports and their status are shown both as a table and a chart. This gives you good overview of the status of the test run.
Updated design of the test run page. Larger text and a more spacious layout make the page easier to read.

Activity log for test runs. Follow who did which changes by going to the Activity tab in a test run.
Link existing bug report to step in test run. Have you found a bug that affects multiple test steps? You can now link it to all of them. Use the More… button in the test step. This will make it easier to understand how to recreate the bug.
Smoother bug reporting from test runs. Do you want test steps copied to the bug report or not? The choice is yours, and ReQtest remembers your preference.
Add new test steps while executing a test run. If you realize while executing a test case that it is missing a step, you don’t have to leave the test run and go to the test case to add it.
Instantly add new test case to test run. You no longer need to go the long way around by navigating to the test run, finding the test case and adding it.
Add new test steps while executing a test run. If you realize while executing a test case that it is missing a step, you don’t have to leave the test run and go to the test case to add it.

See in what test step a bug was found. This makes it easy to go back and understand in what context the bug appeared. Good not only for testers but also for developers fixing the bug.
Test results per requirement. Now you can see directly in the requirements list whether there are test cases for a requirement, and follow how the tests are going. Clear bar charts give you an overview for each requirement.
Execution result in test case list. Do you want to know if your test cases were buggy or not? We’re adding a feature that makes it possible to see execution results in the test case list. A quick glance, and you know how you are doing.

These updates or changes aim to increase your productivity in quality assurance and managing complex data, and improve the output of your IT projects.

Meanwhile, we are soon launching a completely new design for ReQtest, that will better support your processes and methods of working with software projects. We’re also going to release something that will improve how you do exploratory and UAT testing in a not too distant future, and we will keep you updated.