BPMN tests to test-db module... why

[kukeltje]

Can anyone shed a light on this? I'm picking up working on the bpmn implementation again and synched with svn (has been a long time) and saw this for me strange move...

[jbarrez]

Hi Ronald. The aim for the 4.3 release is to have the bpmn2 stuff that currently is in svn revised, docced and examplified/blogified.

Now the change of the test classes was done because
* simplified QA scripts a lot. Testing jBPM = testing JPDL + BPMN
* bpmn2 will be an integral part of jBPM: doc-wise, example-wise, test-wise we want it to be one coherent piece, since this simplifies the management overhead a lot.

For me the most important reason is that the module jbpm-test-db = testing jBPM (= jpdl + bpmn)

[kukeltje]

That was what I suspected, but jBPM = jpdl + bpmn + pvm + .... and the rest is not in the test-db afaics

The thing is I just don't like to have to run tests on 'every' module when I want to change something in the BPMN part. For testing 'full' jBPM, e.g. the examples (kind of integration tests) would be the best.

So I can only partly (<50%) understand this, but of-course will conform to this.

Regarding the 4.3 release, is there some info on what needs to be in it, what not and what has already been done? I'll focus on those parts then as well.

[jbarrez]

I've had the same thoughts when we moved the tests (just a few days ago, actually), so I'm not yet 100% convinced too.

Monday I'm gonna put together an overview (probably wiki) with what and when. The focus of 4.3 is to make the basic bpmn2 stuff visible for the end-users, probably I'll also take in account the excel sheet containing basic, core, extended you sent earlier. I was going to include you and Bernd in the communication anyway. We can then discuss how to proceed and what to do when.

So to conclude: for me the first thing to do is to get an overview what is currently in the codebase. Document it. Write examples (hello world style). I've seen that some parts of the spec have changed (eg Interface) so that needs revision too.

[kukeltje]

"jbarrez" wrote:
I've had the same thoughts when we moved the tests (just a few days ago, actually), so I'm not yet 100% convinced too.

Isn't running mvn install in the root folder the way to test jBPM to the fullest? That is what everybody expects. Having the bpmn tests in test-db is just illogical, certainly in combination with maven.