Is your Software Testing Ad-Hoc?


Photo by Harry Sandhu on Unsplash

We wanted to start the new-year off with a topic we hear a lot about from many many people.

Our Software Testing is Ad-hoc (i.e. created or done for a particular purpose as necessary.).

  • It is never reused.
  • We are always looking at testing each project as if it were a brand new experience.
  • Very little gets carried forward from previous projects and a lot of stuff seems to disappear

If you have heard this or felt this way, you are not alone. The comment that “We had this somewhere but I cannot remember where or cannot find it right now” gets repeated a lot.

The question is why does it occur. Some of the answers are below:

  • Project budgets are not built with the intent of supplying tests to later projects.
  • No-one can predict whether the same testcases will be needed in a future project
  • No-one can predict whether the testcases will be valid for a future project (may be outdated).
  • It is not possible to estimate how long it will be before an update is needed and we might re-use the testcases.

All of the above reasons mitigate against creating and retaining robust testcases suitable for future use. The end result is ad-hoc testcases created for the project and discarded after one or a few uses.

If you want a process that will solve this problem, come back in 2 weeks when we will provide a methodology that will solve this problem at minimal project cost and with positive ROI over the lifetime of the software.

In the meantime, if you are in the GTA (Greater Toronto Area) or KW, see our next blog next week about the coming presentations.

If you cannot wait for the two weeks for an answer look at some of the following information:

Contact us or join the discussion.
Past Blogs
Monthly Newsletter

Older Posts


A Better Way – Case Study 1 – Thinking Outside the Box

A Better Way - Case Study 1 - Thinking Outside the Box In our last several blogs we have discussed 'A Better Way to Test". The issue is to apply this to actual situations. We have 5 Case Studies we plan to use over the next several weeks to address this. The first one...

read more

October QA Events – Toronto and GTA

  NVP Software Solutions will be participating in the following software testing and quality assurance events happening this October in Ontario, Canada. The events are located in Toronto, Kitchener-Waterloo and London in the coming two weeks. Check out the...

read more

A Better Way to Test – 7

A better way to Test - 7 In our last blog we discussed, testing to risk. One of the methods we mentioned to address Risk was testing, even if it was not the only method. However, stating that we should test and actually completing the task are two different items....

read more

A better way to test – 6

A better way to Test - 6 In our last blog we discussed, as the last point in our list, testing to risk. If you have the risks listed, explained, classified, calculated, ordered and entered into a database, it may be easy to attach testcases to them and determine when...

read more

September QA Events – Toronto and GTA

  NVP Software Solutions will be participating in the following software testing and quality assurance events happening this September in Ontario, Canada. The events are located in Toronto, Kitchener-Waterloo and London in the coming two weeks. Check out the...

read more

A better way to Test – 5

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...

read more

A better way to Test – 4

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

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

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

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

Categories