From 80ec52a5177b45b4c60e1ef08bf7ba7a80f2d67c Mon Sep 17 00:00:00 2001 From: Amara Date: Thu, 12 Dec 2024 15:25:04 -0600 Subject: [PATCH 1/3] add note, remove step linking to supported SDK --- .../development/testing-process-definitions.md | 12 ++++++++---- .../development/testing-process-definitions.md | 12 ++++++++---- 2 files changed, 16 insertions(+), 8 deletions(-) diff --git a/docs/components/best-practices/development/testing-process-definitions.md b/docs/components/best-practices/development/testing-process-definitions.md index d6bc992865d..f3fa1cfa969 100644 --- a/docs/components/best-practices/development/testing-process-definitions.md +++ b/docs/components/best-practices/development/testing-process-definitions.md @@ -56,15 +56,19 @@ When using Java, most customers use Spring Boot. While this is a common setup fo ### Technical setup using Spring +:::caution +Spring support with Zeebe Process Test uses the community-supported Spring Zeebe SDK. +Spring support is not available for Camunda 8.6+. +::: + :::caution JUnit 5 You need to use JUnit 5. Ensure you use JUnit 5 in every test class: the `@Test` annotation you import needs to be `org.junit.jupiter.api.Test`. ::: 1. Use [_JUnit 5_](http://junit.org) as unit test framework. -2. Use the [Spring Zeebe SDK](../../../apis-tools/spring-zeebe-sdk/getting-started.md). -3. Use `@ZeebeSpringTest` to ramp up an in-memory process engine. -4. Use annotations from [zeebe-process-test](https://github.com/camunda-cloud/zeebe-process-test/) to check whether your expectations about the state of the process are met. -5. Use mocking of your choice, e.g. [Mockito](http://mockito.org) to mock service methods and verify that services are called as expected. +2. Use `@ZeebeSpringTest` to ramp up an in-memory process engine. +3. Use annotations from [zeebe-process-test](https://github.com/camunda-cloud/zeebe-process-test/) to check whether your expectations about the state of the process are met. +4. Use mocking of your choice, e.g. [Mockito](http://mockito.org) to mock service methods and verify that services are called as expected. A test can now look like the following example. The complete source code is available on [GitHub](https://github.com/camunda-community-hub/camunda-cloud-examples/blob/main/twitter-review-java-springboot/src/test/java/org/camunda/community/examples/twitter/TestTwitterProcess.java): diff --git a/versioned_docs/version-8.6/components/best-practices/development/testing-process-definitions.md b/versioned_docs/version-8.6/components/best-practices/development/testing-process-definitions.md index d6bc992865d..f3fa1cfa969 100644 --- a/versioned_docs/version-8.6/components/best-practices/development/testing-process-definitions.md +++ b/versioned_docs/version-8.6/components/best-practices/development/testing-process-definitions.md @@ -56,15 +56,19 @@ When using Java, most customers use Spring Boot. While this is a common setup fo ### Technical setup using Spring +:::caution +Spring support with Zeebe Process Test uses the community-supported Spring Zeebe SDK. +Spring support is not available for Camunda 8.6+. +::: + :::caution JUnit 5 You need to use JUnit 5. Ensure you use JUnit 5 in every test class: the `@Test` annotation you import needs to be `org.junit.jupiter.api.Test`. ::: 1. Use [_JUnit 5_](http://junit.org) as unit test framework. -2. Use the [Spring Zeebe SDK](../../../apis-tools/spring-zeebe-sdk/getting-started.md). -3. Use `@ZeebeSpringTest` to ramp up an in-memory process engine. -4. Use annotations from [zeebe-process-test](https://github.com/camunda-cloud/zeebe-process-test/) to check whether your expectations about the state of the process are met. -5. Use mocking of your choice, e.g. [Mockito](http://mockito.org) to mock service methods and verify that services are called as expected. +2. Use `@ZeebeSpringTest` to ramp up an in-memory process engine. +3. Use annotations from [zeebe-process-test](https://github.com/camunda-cloud/zeebe-process-test/) to check whether your expectations about the state of the process are met. +4. Use mocking of your choice, e.g. [Mockito](http://mockito.org) to mock service methods and verify that services are called as expected. A test can now look like the following example. The complete source code is available on [GitHub](https://github.com/camunda-community-hub/camunda-cloud-examples/blob/main/twitter-review-java-springboot/src/test/java/org/camunda/community/examples/twitter/TestTwitterProcess.java): From 93d65f368443984723c6c7d03afbb3f555566e67 Mon Sep 17 00:00:00 2001 From: Amara Graham Date: Fri, 13 Dec 2024 08:21:41 -0600 Subject: [PATCH 2/3] Update docs/components/best-practices/development/testing-process-definitions.md Co-authored-by: Philipp Ossler --- .../best-practices/development/testing-process-definitions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/components/best-practices/development/testing-process-definitions.md b/docs/components/best-practices/development/testing-process-definitions.md index f3fa1cfa969..edb3ff10769 100644 --- a/docs/components/best-practices/development/testing-process-definitions.md +++ b/docs/components/best-practices/development/testing-process-definitions.md @@ -57,8 +57,8 @@ When using Java, most customers use Spring Boot. While this is a common setup fo ### Technical setup using Spring :::caution -Spring support with Zeebe Process Test uses the community-supported Spring Zeebe SDK. -Spring support is not available for Camunda 8.6+. +Spring support with Zeebe Process Test uses the community-maintained project Spring Zeebe. +The new Camunda Spring SDK (Camunda 8.6+) is not supported. You could still use the testing library but without hooking into the Spring lifecycle. ::: :::caution JUnit 5 From 940d1ed63d6068a7216a2756e9cdcdad5e28125f Mon Sep 17 00:00:00 2001 From: Amara Graham Date: Fri, 13 Dec 2024 09:59:06 -0600 Subject: [PATCH 3/3] Update versioned_docs/version-8.6/components/best-practices/development/testing-process-definitions.md Co-authored-by: Philipp Ossler --- .../best-practices/development/testing-process-definitions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/versioned_docs/version-8.6/components/best-practices/development/testing-process-definitions.md b/versioned_docs/version-8.6/components/best-practices/development/testing-process-definitions.md index f3fa1cfa969..edb3ff10769 100644 --- a/versioned_docs/version-8.6/components/best-practices/development/testing-process-definitions.md +++ b/versioned_docs/version-8.6/components/best-practices/development/testing-process-definitions.md @@ -57,8 +57,8 @@ When using Java, most customers use Spring Boot. While this is a common setup fo ### Technical setup using Spring :::caution -Spring support with Zeebe Process Test uses the community-supported Spring Zeebe SDK. -Spring support is not available for Camunda 8.6+. +Spring support with Zeebe Process Test uses the community-maintained project Spring Zeebe. +The new Camunda Spring SDK (Camunda 8.6+) is not supported. You could still use the testing library but without hooking into the Spring lifecycle. ::: :::caution JUnit 5