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: