Process Test Coverage Report

By
  • Blog
  • >
  • Process Test Coverage Report
TOPICS

30 Day Free Trial

Bring together legacy systems, RPA bots, microservices and more with Camunda

Sign Up for Camunda Content

Get the latest on Camunda features, events, top trends, and more.

TRENDING CONTENT

As part of the Hack Days this year my colleague Falko migrated an existing tool we (Camunda Consulting) used with success in a lot of projects to bpmn.io: The Process Test Coverage Report Generator. It just hooks into an automated test (typically JUnit) and creates an HTML report showing the coverage:

  • For every Test Case
  • For the whole Test Suite
See this example for one test case – obviously the Happy Path of the process model:

Happy Path of the process model

The report can easily be watched locally within your IDE or hooked into your Jenkins Build. See GitHub Readme for details.
By the way – our Best Practice is to go for “Flow Node Coverage” – so your Test Suite should “visit” each BPMN Flow Node (Events, Activities, Gateways, …) at least once.
Happy Testing!

Try All Features of Camunda

Related Content

We're streamlining Camunda product APIs, working towards a single REST API for many components, simplifying the learning curve and making installation easier.
Learn about our approach to migration from Camunda 7 to Camunda 8, and how we can help you achieve it as quickly and effectively as possible.
We've been working hard to reduce the job activation latency in Zeebe. Read on to take a peek under the hood at how we went about it and then verified success.