And here I am again. I just came back from vacation and already have the urge post an article on this beautiful blog that we have together. We already discussed the near future of testing. One of the things that are changing is the change to standard software packages. These systems should of course be properly tested when installing at the client. I have experience with this package testing when I tested an implementation of PeopleSoft! But we also see a shift where the testing takes place.

More and more clients require that their suppliers provide well-tested software. I state well tested, because they already wanted quality software! By proving the needed prove that the software is properly tested a supplier can count on sales to the client and the client does not have to test it by itself. I think there are some contractual snags, but I am a test manager and no lawyer. For companies that provide testing services to customers they lose clientele. The client is no longer testing by itself. Something that in the current economy is really popular (for the client). A test service provider also use it to an advantage.

With less purely functional testing to offer, but more development testing, a newly created market can be approached. Suppliers often have no idea how to test and then they look to the experts. Only are these suppliers not looking for functional testers. As a result there is a shift in focus on testing software, there still is testing that needs to be done, but at a different level. Development testing can be done on many different levels. It also makes the use of test automation easier. Applications for reading code or simple errors can be applied immediately, but also things like model-based testing can be better deployed during development testing.

Since testing is a form of quality there will also be an important focus on other measures. By determining whether the design of an application really good pick it is a good first step to review or evaluate a document. In this way, a document is ‘tested’ and has defects are found in an early stage. Actually evaluating is just testing! And another good thing; it’s cheaper compared to testing! This is because the errors are removed early and are not build into the application and while testing are newly discovered, which in turn leads to adjustments. This makes the job as a test manager actually simpler.

What should a test manager do? First, a test manager will work even more closely with the Quality Manager. Together they will develop the best strategy for how a project and suppliers can be checked on results. A test manager will therefore have to look into the evaluation and testing strategy. Checking for risks, time, cost and result. A test manager will also require the supplier to establish in what form the communicate on how well (or how bad) there is tested.

Also a end-to-end test will be needed to determine if all the software applications work well together. As posted earlier, this may be in large chains, something most test managers are not prepared for. In the end the client still needs to execute an acceptance test, because that is required by law (at least in the Netherlands). Maybe something of a lawyer in a test manager after all?

The field of a test service provider has changed, but particularly for a test manager. Be prepared!