# "codebase property already set" when running ESIntegTestCase

**URL:** <https://discuss.elastic.co/t/codebase-property-already-set-when-running-esintegtestcase/135659>\
**Category:** Elasticsearch\
**Created:** [June 13, 2018, 9:11am UTC](https://discuss.elastic.co/t/codebase-property-already-set-when-running-esintegtestcase/135659 "2018-06-13T09:11:41Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [June 13, 2018, 10:33am UTC](https://discuss.elastic.co/t/codebase-property-already-set-when-running-esintegtestcase/135659/2 "2018-06-13T10:33:56Z")

</div>

You can not run elasticsearch embedded. Read this [blog post](https://www.elastic.co/blog/elasticsearch-the-server).

Note that to run integration tests (not unit tests) you would probably prefer running that in something close to a production environment, like a real elasticsearch server instance. I shared some ideas about integration testing in this thread: [In memory testing with RestHighLevelClient](https://discuss.elastic.co/t/in-memory-testing-with-resthighlevelclient/106196/6)

---

_[View the full topic](https://discuss.elastic.co/t/codebase-property-already-set-when-running-esintegtestcase/135659)._