# Integration tests - where and how

**URL:** <https://discuss.circleci.com/t/integration-tests-where-and-how/26748>\
**Category:** Running Tests\
**Created:** [November 27, 2018, 12:49pm UTC](https://discuss.circleci.com/t/integration-tests-where-and-how/26748 "2018-11-27T12:49:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![i0natan](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/i0natan/32/23928_2.png) [@i0natan](https://discuss.circleci.com/u/i0natan)\
**Post date:** [November 27, 2018, 12:49pm UTC](https://discuss.circleci.com/t/integration-tests-where-and-how/26748/1 "2018-11-27T12:49:31Z")

</div>

We have integration tests, multiple microservices, Circle CI workflow and Kubernetes based production. We have 3 options about where to run the integration tests:

1. CI local, using the CI vendor run-time - multiple containers that interact with each other using executors. Propietary Circle syntax and run-time

2. Remote Kubernetes - the CI would have to spinup an external Kubernetes env (at our cloud provider) and run the test over there. Simulates our real production but harder to invoke from the CI

3. CI local, using docker-compose - known and reputable technology, yet not a copy of our production

Which is your preferred choice?

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\
**Post date:** [February 25, 2019, 12:49pm UTC](https://discuss.circleci.com/t/integration-tests-where-and-how/26748/2 "2019-02-25T12:49:32Z")

</div>

Closed on February 25, 2019, 12:49pm UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
