# Seeking feedback on local-testing your Compute services

**URL:** <https://community.fastly.com/t/seeking-feedback-on-local-testing-your-compute-services/315>\
**Category:** Compute\
**Created:** [July 13, 2023, 3:29pm UTC](https://community.fastly.com/t/seeking-feedback-on-local-testing-your-compute-services/315 "2023-07-13T15:29:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jaskiratr](https://sea1.discourse-cdn.com/flex019/user_avatar/community.fastly.com/jaskiratr/32/847_2.png) [@jaskiratr](https://community.fastly.com/u/jaskiratr)\
**Post date:** [July 13, 2023, 3:29pm UTC](https://community.fastly.com/t/seeking-feedback-on-local-testing-your-compute-services/315/1 "2023-07-13T15:29:59Z")

</div>

Calling all developers using Compute! Do you use Fastly’s local-testing tool ([Viceroy](https://github.com/fastly/Viceroy)) to run and test your Compute code locally?

We would love to hear your feedback. Share your thoughts on the developer experience, functionality, and any potential improvements or features you’d like to see. Your input is invaluable to us! #DevFeedback