title: Best practice for test and production environments
body: <p>In the company where I work, we have 2 environments: test and production. We are not currently starting a new environment, because of cost.</p>
  
  <p>Here is the procedure we follow: business makes a feature request, development makes it happen and deploys it on test environment. Then business tests it (UAT), and if it's OK, the feature will be included into next production deployment. </p>
  
  <p>The problem is best practices for test DB. Developers treat test environment as their playground, and sometimes they reset the DB to initial state for testing purposes. On the other hand, business people think that test DB must be stable, and should not be reset. We would like to resolve this issue, and decide if test environment should belong to development team or business team. (Developers don't want business to put their nose in test env., but business team is paying for servers.)</p>
  
  <p>What is the best practice about environments? Can you recommend an article about this?</p>