Camunda Process Test

WORKFLOW SKILL: plan segments, author scenarios, run the Maven test command, and close coverage gaps.

DO NOT USE FOR:

Do not use this skill to author BPMN, DMN, FEEL, or forms, deploy to a live cluster, or test UI behavior. Route those tasks to camunda-bpmn, camunda-dmn, camunda-feel, camunda-forms, camunda-process-mgmt, or the relevant UI test framework.

Author and run Camunda Process Test suites for Camunda 8.8+ that reach 100% BPMN element coverage with the minimum number of test segments. Test assertions are limited to reachability and routing — CPT exercises that the engine traverses the right elements, not the data values produced by service tasks or external systems.

Prerequisites

• Java 21+, Maven (or ./mvnw), Docker runtime (OrbStack, Docker Desktop, or Rancher Desktop) — see references/setup.md
• camunda-process-test-spring 8.8+ on the test classpath for Java fallback suites; the instruction-based .test.json format and 8.9-only APIs require 8.9+
• A working BPMN file (lint clean — see camunda-bpmn). DMN and form files referenced by the BPMN must also be present.

For a Node.js layout, set NODE_RESOURCE_DIR and run Maven from the generated test/ directory as described in references/setup.md. The Maven commands below are shell-neutral; the Node.js POM reads the environment variable and standard Java layouts do not need it.