# Shifting to using the correct environments for testing

**URL:** <https://talk.openmrs.org/t/shifting-to-using-the-correct-environments-for-testing/2070>\
**Category:** Development\
**Created:** [June 3, 2015, 1:56pm UTC](https://talk.openmrs.org/t/shifting-to-using-the-correct-environments-for-testing/2070 "2015-06-03T13:56:39Z")\
**Posts on this page:** 1\
**Showing post:** 28

<div class="post-metadata">

**Author:** ![burke](https://talk.openmrs.org/user_avatar/talk.openmrs.org/burke/32/17_2.png) [@burke](https://talk.openmrs.org/u/burke)\
**Post date:** [August 31, 2015, 8:04pm UTC](https://talk.openmrs.org/t/shifting-to-using-the-correct-environments-for-testing/2070/28 "2015-08-31T20:04:17Z")

</div>

> [@surangak](#):
>
> For the new machines, which should/could I use for our work on FHIR?

You can make a request to the helpdesk for a new machine and they can help assign a server based on the need:

- Demo/playground: devtest
- Integrated (automated) testing: int
- Quality assurance (manual) testing: qa
- User acceptance testing for a specific relase: uat

If you’re unsure, it’s probably a devtest server.

Ideally/alternatively, since you are aiming to get FHIR into Platform 2.0, get the FHIR module included in the distribution of the Platform (so it would be tested & deployed to int‑platform, qa‑platform, and, when we begin testing for the 2.0 release, uat‑platform.

---

_[View the full topic](https://talk.openmrs.org/t/shifting-to-using-the-correct-environments-for-testing/2070)._
