Skip to main content
5 answers
  1. Jan 4, 2019, 9:05 PM

    Just adding my 2 cents ...

     

    Depending on the software & hardware resources available, you can have separate environments.

     

    In one of my projects, which was a big company and so big budget infrastructure, we had separate environments for DEV, QA, UAT & PROD where we had separate physical severs for each. Though I am not too familiar, we used to use Bamboo for automated deployment to each environment. We as developers used to develop our projects, drop in a pre-assigned location and then on Bamboo used to take over for automated deployment to different environments. However I am told there were limitations and quiet a few challenges DEVOPS group faced. Some teams also used Jenkins to the automated process.

     

    In another of my projects, which was a low budget environment, we had just two servers. One server hosted DEV & QA environments. These were just two separate folders named DEV & QA on same Site. We used to manually move the files from one env. to another. The other server hosted UAT & PROD. Some teams prefer to have UAT also along with DEV, reason being, the UAT load should not take up resources from PROD which could be more mission critical. However we had UAT on PROD since the Prod server traffic not a whole lot and we intended to do UAT actually mimicking PROD infrastructure rather have any last minute surprises as far as an hardware based performance issues go.

     

    Other than that Richa has done a great job sharing exhaustive listing of most popular testing tools that we have also used most of the time.

     

    So bottom line is, it depends on what your situation and whats acceptable to PMO office. Everything costs  ...  Hope this helps... Goodluck !!

0/9000