Doorgaan naar hoofdcontent

Test driven development with BPMs

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

  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:   

Labels:

Reacties

Een reactie posten

Populaire posts van deze blog

OSB 10gR3 and SWA and MTOM

This blog is about using soap with attachments and the use of MTOM within the OSB (10gR3). A service is created that accepts a soap with attachment (DocumentService) and translates it to a service that accepts a binary element. MTOM is used for performance reasons for the second. Some notes: * For the use of attachments you need RPC-style document instead of the usual document-style. This due to the fact that the document-style limits a message to a single . * A service can not have both SWA and MTOM within OSB. First a WSDL is setup for the DocumentService: The $attachments variable holds the attachments and the body holds the attachment data. Also other data is stored within the attachment element (see h
12 reacties
Meer lezen

Microservices mindmap

"The tree" - See also   my photo page When you are fairly new within the Microservices land, there are a lot of terms fired at you. So also for my own understanding i have made a mindmap. I think it has a good status now, so that i can share it with you. As always feedback is very welcome ! You can download the mindmap here .
47 reacties
Meer lezen

Book review: Data Management at Scale (Piethein Strengholt)

 This blog is a review of the book "Data Management at Scale (See also at bol.com ) Data Management is a hot topic nowadays and this book does a fantastic job at adding value to this topic. It is a must read and one of the few technical books I finished reading in a weekend. The book gives a fantastic overview on how to implement a Data Mesh data architecture. The Data Mesh concept is explained by Martin Fowler here . The book is a good mix between conceptual and implementation architecture level. It gives a lot of examples of how this architecture at scale can work, for both small and big companies. It is practical and I used it to implement it at one of my customers. The book describes an architecture in which the focus is on the DIAL (Data- and Integration Access Layer).  On a high level the book covers the following topics: The key principles for data management at scale - Domain-Driven Design  - Domain Data Stores - Meta data management Ready Data Store The concept of servin
5 reacties
Meer lezen