Next year (Monday) I will be starting a new assignment. After 4 years with the same customer I may go up and perform an end-2-end test for one month.

Actually end-2end testing is one of the most difficult tests there is. Functional everything should work fine separately and with the end-2-end test all the systems in the complete process should be linked with each other. A small mistake in one of the substantive systems and everything goes wrong. Therefore, everything should really be good. Unfortunately some systems (read ‘departments’) sometimes speak a different language with each other. Because when ‘System X’ delivers something else compared to what ‘System Y’ expects there is a mismatch on the content. Thus, the (functional) specifications are not correctly discussed with each other, communication!

Now how do we solve this? One way is to run a paper end-2-end test in preparation for your end-2-end test. What is a paper end-2-end test? All parties sit down with each other and talk through the process that takes place within the systems. By creating a transparent flow of the process with all parties present this yields to a number of advantages, namely:

1. Possible mismatches in the specification are found;
2. These mismatches are transparent and can directly be discussed;
3. The test specifications with attention to the end-2-end test are a lot simpler because the actual process has been made visible to/by all parties, and
4. Everyone has the same mindset with the end-2-end test, making communication better and easier.

Actually all very valuable advantages that are very easy to make possible.

However it’s a more challenging task to provide an end-2-end testing environment. Within the complete end-2-end test you would want use the most realistic test environment as possible and with real-life data. How do you get everyone to find out where everything is and wait for your signal? The answer to that question is: “not”, at least in complex end-2-end chains with more than 5 systems. And if you have mastered this, you’re the exception that confirms the rule. It is almost impossible to link multiple systems together with the same data. Only if you can enter the test cases physically into all the systems. A choice you can make when time and resources play no role. But usually it is not, so this is almost impossible. If you’ve been successful with this I am very curious how you did it? Please let me know …

In order to properly set up an end-2-end test that communication is needed again. Communicate with all the parties what they can expect and what you can expect. In such a way you make the testing process more transparent and everyone can watch what you do. But it also can create improvements on the process by experts from the systems. These experts can see where it all must meet and make adjustments when needed.

Actually, the final test is always one (part of) an end-2-end test. This to make sure everything in the process is functioning correct. Similarly at the end of the year …

Next year I hope to tell much more about this I will keep everyone post, where possible. But for now, watch out with fireworks and a happy new year and good luck in 2009!

1. M. Welters Says:
   September 18th, 2009 at 08:02

   Hoi Ewald, leuk om je toevallig tegen te komen. Ware woorden over ketentest. Weet je de oplossing al?
   Papieren ketentest is een perfecte oplossing maar doorgaans slecht uitgewerkt. Een perfect uitgevoerde PKT kan in mijn ogen bakken met geld besparen binnen projecten. Met vriendelijke groet, Melvin