# Bringing it to next level - Integration testing/Unit testing

**URL:** <https://forum.camunda.io/t/bringing-it-to-next-level-integration-testing-unit-testing/9491>\
**Category:** Discussion & Questions\
**Tags:** process-engine\
**Created:** [October 31, 2018, 10:10pm UTC](https://forum.camunda.io/t/bringing-it-to-next-level-integration-testing-unit-testing/9491 "2018-10-31T22:10:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![camunda\_sailor](https://forum.camunda.io/user_avatar/forum.camunda.io/camunda_sailor/32/13524_2.png) [@camunda\_sailor](https://forum.camunda.io/u/camunda_sailor)\
**Post date:** [October 31, 2018, 10:10pm UTC](https://forum.camunda.io/t/bringing-it-to-next-level-integration-testing-unit-testing/9491/1 "2018-10-31T22:10:17Z")

</div>

Hello Camunda Fridends,

I have been writing code for external services, designing flows, writing scripts. It’s been a delightful ride with Camunda so far!

Now it’s time to bring it to the next level… testing, integration testing, functional testing.

I look up to you wizard for the advice, what’s the best way to ensure that everything will work in production before moving to it. I don’t want to spend my life to click through tasklist/cockpit/my custom app every time some refactoring happens.

Would you have any advice from the field experience? I use almost entirely external scripts. What’s the smart way to do it?

Unit tests are relatively simple but what about integration testing. Most of my code are external services using nodejs.

Thanks, K

---

<div class="post-metadata">

**Author:** ![StephenOTT](https://forum.camunda.io/letter_avatar_proxy/v4/letter/s/d2c977/32.png) [@StephenOTT](https://forum.camunda.io/u/StephenOTT)\
**Post date:** [October 31, 2018, 11:56pm UTC](https://forum.camunda.io/t/bringing-it-to-next-level-integration-testing-unit-testing/9491/2 "2018-10-31T23:56:42Z")

</div>

Check out examples in this repo [https://github.com/DigitalState/Camunda-Spock-Testing/tree/master/End-to-End](https://github.com/DigitalState/Camunda-Spock-Testing/tree/master/End-to-End)

Has prob most of the examples you are looking for.

---

<div class="post-metadata">

**Author:** ![system](https://forum.camunda.io/uploads/default/original/3X/5/8/58d50142eacca605d35cb1ef9e6b86ae85f49436.png) [@system](https://forum.camunda.io/u/system)\
**Post date:** [January 30, 2024, 11:25am UTC](https://forum.camunda.io/t/bringing-it-to-next-level-integration-testing-unit-testing/9491/3 "2024-01-30T11:25:51Z")

</div>

Closed on January 30, 2024, 11:25am UTC


