A better way to Test – 5
In our last blog we discussed how more testing or a higher percentage of test case coverage does not necessarily lead to better testing. We did not, however, provide a solution to the problem.
One of the first items is to classify the testcases. In a project of any size, with numerous testcases, it is difficult to determine what each testcase is doing without classifying them. The Test Management tools allow for a lot of this and it is usually simply a matter of selecting the fields you want to use for classification; providing a limited list of choices for most of the fields (some can be freeform text entry but some need to have a limited number of choices so as to allow classification) and deciding where each testcase belongs. It will not be perfect the first time but can be refined over time. Some items that can be used for classification are as follows:
- Requirements (this comes out of Traceability).
- Function tested (may be a subset of the Requirements or it may be a separate mapping).
- Date of testcase creation (just so you know how old it is).
- Priority of the testcase.
- Some statistics generated from the testcase execution.
- The risk it tests – we have rarely seen this explicitly listed.
The last item is the most important if you are testing against risk. It presupposes that you have the Risks listed, classified and numbered. Then it is a reasonably easy process to link the testcases.
When your project is over, you can determine if the testcases addressed the risks (where appropriate) and whether they are useful for next time.
Take a look at some of the seminars that we offer that address this situation and see if they apply to your situation. Testing can be better.
Contact us for further information.
Photo by Samuel Zeller on Unsplash
A better way to Test - 4 In our last blog we discussed addressing Risk via Testing and one of the problems. Today we want to continue with another of the problems. "More is NOT necessarily Better". Traceability has come a long way in the last few years. Many of the...read more
A better way to Test - 3 In our last blog we discussed the determination of risk. The question is what to do with it when we have completed that work. While there is a temptation to write a testcase for every risk; that is not always possible. A testcase or testcases...read more
A better way to Test - 2 The second item to determine is the Risk. We always guess that, if you gather three people from the project together and ask them what the risk is, you will end up with 4 answers: Three from the people at the meeting and the right one that...read more
A better way to Test - 1 The first thing to determine is the type of project, type of methodology being used to build it and the people involved (All of them) in building the project. This is not new by any means and seems obvious information to gather, but in the...read more
Isn't there a better way to Test? This is a question that gets asked very frequently especially at the end of projects that have not gone well. Testing is often left to the end of the project and by the time people get to it they are tired of the project, tired of the...read more
In the last couple of blogs we talked about Early Involvement and the ROI of Quality Assurance. A list of a few places where Quality Assurance pays was also provided. However, Selling Quality Assurance can still be a challenge. Some organisations see the benefit and...read more
NVP Software Solutions will be participating in the following software testing and quality assurance events happening this June in Ontario, Canada. The events are located in Toronto, Kitchener-Waterloo and London in the coming two weeks. Check out the relevant...read more
One of the items which comes up in most Quality Assurance discussions is the determination of what Return on Investment Quality Assurance provides. It can be hard to justify and obviously depends on the Costing Model used in your organisation. The factors in the...read more
One of the items which comes up in most Quality Assurance discussions is the determination of when to involve Quality Assurance in the project. Those with the traditional view of Quality Assurance as simply Software Testing (Quality Control) delay the arrival of the...read more
NVP Software Solutions will be participating in the following software testing and quality assurance events happening this May in Ontario, Canada. The events are located in Toronto, Kitchener-Waterloo and London in the coming two weeks. Check out the relevant...read more