citrusframework / citrusframework/citrus

Parallel citrus build tests

Open
#377 0 comments 0 reactions 0 assignees View on GitHub
enhancement prio-medium
Dominant language
Java
Stars
485
Forks
155
Avg merge
4d 22h
Merged PRs (30d)
6

Description

Currently, a Citrus build takes a while. To provide fast feedback of changes to the developer through the CI/CD Pipeline, one should parallel the integration tests.

At least one has to ensure that the integration test use dynamic ports on the build server so that the citrus endpoints don't clash.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.