Test driven development with BPMs


I have read a book about Test Driven Development written by Kent Beck. This is a very famous and good book about test driven development with Java. This technique can also be adapted when developing a Service Oriented Architecture or implementing BPMs. For example with Cordys. This blog describes some guidelines.

Some Guidelines

  1. Be sure to write your BPMs with as less context as possible
    This means that the context should be given as a parameter for example. In this case you can use soapUI or SOATester to test the BPM independently of the other BPMs.
  2. Each time there is an error within the BPM, be sure to write a test case for the error that shows the error
    After that solve the error and this way the test set also becomes bigger.
  3. Just like with the technique described within the book, you can start with writing the soapUI scripts first and then implement the BPMs
    This way your test cases should represent the exact requirements for the BPMs.
These are just some guidelines which are easy in theory but of course always hard in practice. But the message is also that you should consider the test fullness of your BPMs and Services. Only this way you can refactor your architecture with confidence. It also emphasizes that testing must be considered as soon as possible within your programs.

Please feel free to react and ask questions.

For completeness i have added a link to the book:   

No comments:

Post a Comment