jBPM's Integration Test Scenarios

Scenario 1: Task forms

Prerequisites: unzipped jpdl suite distribution

This scenario will check at least following features:

• Create the complete process with the graphical designer

• Generate a start task form

• Generate a task form

• Group assignment

• Personal assignment

• Reassignment

• Deployment from the designer to the runtime engine

• Walk through the process participant part of the console

1. New Project wizard.  Use project name 'taskforms'

2. Select the jpdl source folder

3. New jPDL Process wizard.  Use project name 'taskprocess'

4. Add start-state 'start', end-state 'end' and 3 task nodes

5. ...

Below is just a proposal.  "How low can you go?"   How detailed would we specify these scenarios.  Is this the right level ?

Scenario 2: Automatic job scheduling

Prerequisites: unzipped jpdl suite distribution

This scenario will check at least following features:

• Create the complete process with the graphical designer

• Nodes with an action as the behaviour

• A complete process without tasks

• Asynchronous continuations

• Timer

• Finding the process instance in the console (process should have at least one plain wait state)

• Signalling the process instance through the console

Scenario 3: Email

Prerequisites: unzipped jpdl suite distribution + the email test war

This scenario will check at least following features:

• Create the complete process with the graphical designer

• mail-node and mail action

• Task with notification and reminder

Scenario 4: Superstates

JbpmDbTestStatus