Architect Consultant blog

It is not enough for today’s software developers to know their programming language well. There are further skills, that more and more companies are expecting from there employees. One of the most important is  Test Driven Development  (TDD). This is not an introduction to TDD. If you want to learn it, I recommend  Uncle Bob’s  awesome  Clean Code Videos  (Episode 6 - TDD) or simply  ask Google  for it. But many developers are writing bad code and applying TDD does not make them writing good code. Instead it makes them also writing bad tests. So this is about writing better test code. Applying simple rules To understand why test code can be bad, you should understand, what it should do. It should work as the parachute, that keeps you alive, when refactoring your code. Tests may help you to be sure nothing breaks, when adding new features to your code. But tests may also work as sample code, that documents your APIs better than any other doc...

Introduction 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 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. 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. 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 ...