[MGNLWORKFLOW-37] As a developer I can test that the jBPM integration works to be sure that starting, querying, .. is working Created: 28/Feb/13  Updated: 07/Aug/13  Resolved: 07/Aug/13

Status: Closed
Project: Magnolia Workflow Module
Component/s: jBPM
Affects Version/s: None
Fix Version/s: 5.0

Type: Story Priority: Critical
Reporter: Jozef Chocholacek Assignee: Daniel Lipp
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLWORKFLOW-30 Implement JbpmWorkflowManager.dispatc... Closed
is related to MGNLWORKFLOW-31 Implement JbpmWorkflowManager.notify(... Closed
is related to MGNLWORKFLOW-26 Make the modules to start with the ne... Closed
is related to MGNLWORKFLOW-29 Implement JbpmWorkflowManager.launch(... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: Workflow

 Description   

This is rather sort-of an integration test than unit test.

Things to test:

  • start/stop Knowledge & Human Task service
  • launch workflow
  • find waiting human task for user, when the task was directly assigned to a user
  • find waiting human task for user, when the task was assigned to a group the user is member of
  • dispatch human task
  • ? send a message to user/group from within a human task


 Comments   
Comment by Daniel Lipp [ 07/Aug/13 ]

JbmpWorkflowManager has been made testable with MGNLWORKFLOW-70 - other things like the Human Task related ones have become obsolete with MGNLWORKFLOW-81

Generated at Mon Feb 12 10:06:10 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.