Bugtracking

ReQtest – Requirements and Testing – A Great Pair

Times are changing, and as usual, technology is a step ahead. How do we adjust to the present situation in which we, as quality management specialists, need to face new challenges? We need to always guarantee the best quality, high availability and great usability, all within a short time, with small budgets and without too much stress. What will help us, the same which makes it difficult, are new tools, tailored to our requirements. One of them is ReQtest. ReQtest is a cloud-based software for managing requirements, test cases and bug reports.

ReQtest is short for “Requirements and testing” and you can choose to use only one part of ReQtest or all parts as they are seamless integrated. The more parts of ReQtest you use the better traceability between items stored in ReQtest. I am a big fan of doing business analysis in an atomic way. What does ‘atomic requirements’ mean ? I think that this question is for another article, but the key assumption of this idea is to have a set of business stories which have full traceability. Traceability sounds complicated but just means that you can see the relations between requirements, test cases and bug reports. With the powerful built-in traceability matrixes you can find requirements that lack test cases and judge the test-impact of a proposed change among many other things.

Easy to use and to get started with

Since ReQtest is cloud-based you don’t have to install it on your own server. Installation of upgrades is maintained about once a month by the supplier. ReQtest’s usability is strong and it is very easy to get started. Your testers definitely don’t have to go through a 3-day training seminar to get started. The help documentation is extensive and support via e-mail and phone is included in the price. To get started there are several video-tutorials available on the web. You can add more users during intensive test periods and remove users when testing is completed, so as to adjust the pricing of ReQtest.

Similarly to other QA tools, you use forms to enter requirements, test cases and bug reports. These forms are highly customizable by the customer and the search and filter functions are very powerful.
Let’s see how ReQtest can be used to manage requirements, tests and to execute tests and follow up on the progress!
Requirements management
Requirements are the basement for ReQtest, most important for doing it right. You fill in requirements in a form that consists of individual fields. When you create a project in ReQtest you get a bunch of default fields like title, description, type of requirement, priority, status and name of the release that the requirement is going to be released in.
These fields can be renamed or deleted. If you lack some kind of information you can simply add new fields. You can also change values in drop down fields. If you e.g. prefer to use the MoSCoW scale (must, should, could, won’t) when prioritizing requirements, you can easily configure ReQtest to use it instead of high/medium/low. Configuring ReQtest is quite straightforward and applies to requirements, test cases, test runs and bug reports.
ReQtest supports both traditional development and more agile approaches. In an agile project you might want to replace description with “user story”, use the MoSCoW scale for prioritizing, and replace release with sprint.
Requirements can be arranged in a hierarchical view similar to folders, subfolders and files on a file system that is very intuitive and easy to manage (drag and drop). On the screenshot you can see that the tree view is complemented by a table that shows details for each requirement. In the table view you can easily sort, export and search. The search functionality is powerful and frequently used searches can be stored and easily retrieved.
Tests and test planning
In my opinion the modules for planning and executing test cases together with the bug reporting module are the most powerful parts of ReQtest. ReQtest allows you to create and link items between the modules without problems, and what is better is that it also allows for a neat test plan management. What is a test case? Are there standards for that, and does ReQtest conform to these standards? Both answers – Yes. A test case describes the test steps that the tester is to perform to test a certain ability of the system under test. All or some of the test steps have expected results that the tester uses to check if the test was successful. ReQtest has a very easy to use interface to create, manage and plan testing.
To complement test cases ReQtest contains something they call checklists and which have similar structure to the test cases, but serve somewhat different purposes and in certain situations are easier to use than test cases. Checklists are very useful during the implementation, installation and environment and system preparation for testing.
How to manage a large number of tests? A typical test activity like system test or acceptance test often consists of a large number of test cases and checklists that are to be performed by different testers. During test planning ReQtest offers the ability to group items into test runs. Test runs can be grouped by e.g. tester, subsystem, type of test and even after the test methodology. ReQtest is very flexible and the grouping depends only on you and on your experience.
Test execution
We have already grouped and planned tests, so we can begin testing. Test executing is nothing but a passing successively through test runs created earlier. Each step test can be passed, or failed. When creating bug reports based on test cases, ReQtest collects information about the test steps and expected result from the test case into the bug report to speed up the process. Usually the tester only has to complement the bug report with the actual result. For developers this leads to bug reports of higher quality since they always contains steps to reproduce, expected result and actual result. Traceability is maintained automatically so it is easy to use the great functionality that is the traceability matrix. As a test manager it is easy to follow the progress of test execution for a specific tester and for the group of testers.
Reporting
Apart from the already mentioned traceability matrix and searches, in almost every list screen, we can look at the chart, presenting data in a matching context. The report also contains the error trend graph, which is ideal for managers to ensure the quality of reporting.
If the reporting supplied by ReQtest doesn’t fit your test report template you can export your data and create diagrams and reports other applications such as Microsoft Excel.
Summary
As you probably noticed I am a fan of cool gadgets, whether ReQtest is one of them? I think that yes, there are some things which are missing, as they say in a moment, but the overall picture gives a lot of positive signals.
What are the ills of this application? In my opinion a few. Sometimes low usability, as reflected in a strange location of important buttons like “create a test suite”, “add a test suite, ” or even “Save”.
I encourage you to use such tools, are an incredible help for the entire IT team, in conjunction with the requirements tracking offer a lot of added value, which is so urgently needed.
The folks at ReQtest are offering a free, all feature accessible trial for TestAndTry readers. Get your free trial here!

Discussion

3 comments for “ReQtest – Requirements and Testing – A Great Pair”

  1. sweet…nice

    Posted by renu | May 31, 2011, 7:19 am
  2. Great tool, and great article

    wrote a deep review on it, which will be published soon at http://www.qatestingtools.com/reqtest

    Posted by Yuval | March 14, 2012, 12:15 pm
  3. You can find link to this article at http://www.qatestingtools.com/reqtest

    view section ‘File & Media’

    Posted by Yuval | March 15, 2012, 1:47 pm

Post a comment