Result-driven testing can be applied with any testing method. Choosing for TestGoal does not eliminate other possibilities. Result-driven thinking is a guide for the activities that are to be carried out. The method that is handled fills in the activities. However, it would be very pleasant if the method that is handled does support result-driven testing. TestGoal has been developed on the principle that the expertise of the testers, the test principles and the method need to integrate among each other and have to support each other. In TestGoal, result-driven thinking and result-driven practice create a unity. From this, a test method emerges that puts the result of the business in the first place.
The TestGoal-approach supports the tester in applying his expertise and knowledge, and in handling the test principles. On the basis of a clear plan of action it is indicated when activities should be performed, what these should consist of and what the central points are in this matter. When necessary, the plan also gives distinct information about the ‘best practices’. The method supplies the test procedure with a clear structure, by which also less obvious aspects will be accounted for. Also, the communication among project members will be more efficient and the anticipated results are known in advance. By this, a decisive start of the activities is made possible and trust is built right from the beginning.
In short, the TestGoal method assists in operating the test procedure in an efficient way and is completely focused on the result, that is, adding value for the client. This is why we call it ‘TestGoal, result-driven testing’.
