Do you know the difference between trying-out and testing? Rest assured, we are not going to have a semantic discussion here. But what we do want to say is that we see roughly two tastes when it comes to application testing. Namely companies that try out applications and companies that test applications. And there is a world of difference between them!
It is actually serious to note that many organizations in our highly automated society do not test software but try it out. Even more serious is that senior management often has no idea of application testing. It is seen as a nuisance or too expensive. Only when something goes wrong critical questions are asked.
Testing applications requires ownership, process descriptions, planning & coordination, test knowledge, time, discipline and professional tooling. However, as soon as there is incidental testing of (new) software, reporting in spreadsheets and a lack of will and execution, we can speak of trying out applications.
Strangely enough, trying out applications often turns out to be the practice. We find that worrying. The Testersuite team encounters this situation daily. And certainly not with the SME around the corner. On the contrary.
Even more disturbing
Even more disturbing is the sharing of test results. Here we see that two or more organizations that use the same application, testing releases simultaneously. This promotes false certainty. How can you be confident that a module that is relevant to you has been well tested by a fellow company? OK, you use the same modules of an application but is the configuration exactly the same? Are the quality requirements at the same level? Are the testers of the caliber as you yourself have trained? And so on…
Suppose that companies A, B and C simultaneously test the same release of an application. The test results are shared during the test process. When assessing risks, the focus is largely determined by the test results of the colleague companies that are also testing. Modifications that have already been tested by fellow companies and that have not produced any bugs will naturally receive less focus. Here comes the risk of false certainty, which can lead to a wrong focus. It may well be that the design of the application differs or that the colleague companies have not tested it properly. A modification does not receive sufficient attention in the test process and problems arise in production. Feel free to assume that we have many practical examples where this has gone very wrong.
Dealing wisely with sharing content
Sure we see in practice that it can be useful to share content (for example test scenarios) and test results with fellow companies that test the same applications. Testersuite also offers functionality to do this. Just don’t overestimate the added value. Every company will still have to make a risk assessment itself and test the modifications from a release. Watch over the risk of false certainty!
Don’t think too lightly about application testing
Our message is “don’t think too lightly about testing”. Testing applications is a profession and not a matter of trying it out. Fortunately we speak to many test coordinators and test managers who know what they are talking about. We see their daily struggle against higher management. We would therefore like to support them in this.
Sign up here for the latest Testersuite news or scan the QR code.
Who we are?
As a leading player in the test tooling market, Testersuite is constantly helping organizations to take the testing process to a higher level. We believe that smarter and better testing of software – and therefore a mature testing process – contributes to reducing risks and errors and therefore happy users. With our SaaS Tester Suite tool we have taken the testing process of many different companies to a higher maturity level. Think of healthcare institutions, housing associations, municipalities, provincial governments, logistics organization, utility companies, etc … Do you want to know more about Testersuite and the experiences of our customers? Do you want to go through different customer cases with us? Then look here or request a demo below.