# Testing a Replicated.com build

**URL:** <https://discuss.circleci.com/t/testing-a-replicated-com-build/10398>\
**Category:** Build Environment\
**Created:** [February 16, 2017, 4:49am UTC](https://discuss.circleci.com/t/testing-a-replicated-com-build/10398 "2017-02-16T04:49:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ken](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/ken/32/2774_2.png) [@ken](https://discuss.circleci.com/u/ken)\
**Post date:** [February 16, 2017, 4:49am UTC](https://discuss.circleci.com/t/testing-a-replicated-com-build/10398/1 "2017-02-16T04:49:29Z")

</div>

This seems somewhat meta…

Like you, I am using [replicated.com](http://replicated.com) to build an enterprisey, on-premise, product for our customers. I’d like to run some integration tests against the “build”. Do you have any suggestions for setting up the build environment? I’m using their private repos, plus a “bunch” of public containers. For a true-to-life black box test, how do you get your test suite to talk to the web app running in the container? etc.

---

<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:** [June 18, 2018, 11:39am UTC](https://discuss.circleci.com/t/testing-a-replicated-com-build/10398/2 "2018-06-18T11:39:10Z")

</div>

Closed on June 18, 2018, 11:39am UTC