Junari Standard System Environments: Dev, SAT, UAT and Production

• Production
  • This is your live system which is used for your day to day operations, once you have confirmed you are happy with changes in UAT we copy over changes to the live system
    
    
• Staging: UAT - User Acceptance Testing - For Customer Use
• Purpose: for final approval of changes before they are pushed live
• This is a copy of the live database with the latest stable Junari code on it
• Junari will advise the customer when they are updating this, and the corresponding tasks in our project management system will be set to Client to Test
• Once you have approved changes on this system, they can be moved to the live system
• Logins the same as your live system
• Used for testing + proving support issues
• Used for testing + approval of data import
• This can be periodically refreshed with data from the Production system
  
  
• Staging: SAT - System Acceptance Testing - For Junari Use
• Purpose: for integration / system acceptance testing of the vary latest changes made by Junari
• This is the test system we 
• This is used by Junari BAs / Testers for testing brand-newly developed tasks, and can be used by you if you want to look at the very latest changes that have not been fully tested by us yet.
• periodically we will move code from this branch over to the UAT branch, when it has reached a table state
  
  
• Development - Junari developer local machines
  • Purpose: initial development and testing of system changes

  
  

Keywords:

Test environments

Deployment environments

Code environments

Code stages

Deployment stages

System environments