Is Unit Testing Suitable for BPM Development? -

I am currently working on a large BPM project at work which uses the Global 360 BPM tool-set Procession 360 says. Give some background; This product works like many other BPM solutions, in which you create many "process maps" that define the flow of a particular business process that you are trying to model, and in the process of each process There are several function nodes connected together which do special functions (calling web-services etc.).

We are currently experiencing some very serious issues during our release QA phases because there is no way provided by Tool-Set to automate testing of the device maps. So when a large and complex process is developed and assigned to our testing team, there are often a large number of issues that crop up, obviously you have to some issues to exit QA I was hoping that many types of bugs could be seen during the development etc. If we have some type of automated test framework which we have to create a set of unit tests Emal you can, which proved to different routes in the process maps (maps) are.

At this time there is only real development test which is according to functional testing, developers who are documented as a group of test-cases per manual steps. The problem with this approach is that it takes a lot of time for developers to run manually, and due to this, it is relatively comparable to the error also, because we usually were on a very tight schedule Often, often tests are not adequately performed to spot on the spot.

As I said earlier; There is no way provided by the current tool-set to do this type of automated test. Who was really thinking about me? Being very new to the whole BPM scene, my impression was that it was only a product reduction, but I also wonder whether "unit testing" has not been traditionally done in the BPM world? Maybe it's not just suitable for this kind of work?

I know that anyone else has to face such issues anytime, else - if anything - can be done, improve things.

I have tested "unit" with KNen 2003 2003, another commercial BPM I actually I call this integration test because it requires a test server and it is relatively slow though it is automatic.

This book has a good discussion about it (it's also applicable for K2.net 2003).

To apply it to your platform, the device set should have an API that can work on early instances of the process, getting work items, completing the job items etc. You write a test using any supported language (I have used C #) and a test framework (I have used NUnit). If API supports synchronous calls, then it is easy to do.

Start the process under test

progress the task point to a decision point

Set the appropriate process example data

Work Complete the item

The work item is now on expected activity

Delete or complete the process instance

By using the base test classes or helpful methods It can be easy for you to write a map test too.

Basically you want the "test coverage" of the process / map - test each decision point and the correct branch of insurance is taken.