We are not disclosing the testing environment of the company, but i want to tell u, we setup the different testing environment for manual testing and automation testing. As per the requirement of the project and product as well we can setup that environment through build, properties etc deployed on the servers.
Dev Environment:- Every tester or QA don't faith on dev environment and do not verify the functionality or a bug on DEV servers. We will setup the QA environment which is similar to production environment.
QA has own responsibilities to setup the QA environment as per our requirement. We should know to how deployed the build and other related commands related to you linux server-- if you have.
Otherwise have desktop application no need as to setup it -- just copied the code and run it.
Dev env. is env where application is developed and developers are using the application whereas Testing env. is env which is provided to QA team for testing of that applications.
So, QA team always test the application/software in QA enviornment only. Whenever developers are delivering build with changes or new implementations, we need to deploy that build on our QA enviornment so that we get those functionalities for testing.
Well, that is very exceptional case.... still if such things happen, we performing testing on Development Environment because ultimately both are identical but developers keep updating application in their enviornment to check their development.
Actually we can test the application in development enviornment but for that we need to freeze the developer's changes in the application which will affect developer's work & time line.
1) Have a close look at the planned/unplanned maintenance or support events w.r.t Environments
2) Plan, prioritized my task according
3) Raise early flags in case of environmental inconsistencies or failure.
4) Open the escalation window to closure of the failures.
Risk is minute if planned before, extreme risk are acceptable if communicated efficiently.