# Design Recommendations for Testing on Pynq

**URL:** <https://discuss.pynq.io/t/design-recommendations-for-testing-on-pynq/3996>\
**Category:** Support\
**Created:** [April 7, 2022, 10:30pm UTC](https://discuss.pynq.io/t/design-recommendations-for-testing-on-pynq/3996 "2022-04-07T22:30:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rngsys\_a](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/rngsys_a/32/2988_2.png) [@rngsys\_a](https://discuss.pynq.io/u/rngsys_a)\
**Post date:** [April 7, 2022, 10:30pm UTC](https://discuss.pynq.io/t/design-recommendations-for-testing-on-pynq/3996/1 "2022-04-07T22:30:00Z")

</div>

Hey all, I’ve been working on designing a project, and for this project I found that it was easiest to develop the high level Python code separate from the PYNQ implementation specific code, especially for testing the design. Would it be possible/advisable to run these two programs separately and have them communicate over localhost or other communication method? Or is there a recommended method to interface between the two codebases, so that I could essentially connect them together when needed?