Tag Info

Hot answers tagged

2

QA and UAT have different goals. From a commercial stand point QA is there to make sure the clients will accept the version during UAT. After UAT, taking it into production and making sure the client does not run into (to many) critical issues. Client UAT is there to verify clients do not take a version into production that does not meet their minimal ...


2

Run all the tests just right after the build as soon as possible, before deploying to the test environment. Developers should have feedback about their check-ins as soon as possible. Also you say the test-env is used for manual testing, why would you want to risk deploying a non working build. Certainly if you could have run the tests first. In short the ...


2

If QA and DEV environments are equal (have the same dependencies installed, the same build, etc.), there is no much sense to run acceptance tests on both of them, since it will be just duplicated execution and additional overhead in terms of analysing test results on two environments instead of one. Acceptance tests are the tests which provide you ...


1

to my experience in automation test, it is more valuable to run in qa environment but you should communicate with developer frequently on changing part which may affect your automated test cases so you can prepare your automated test cases during development phase and give priority to more static features of the product to prevent updating automated cases ...


1

As a rule of thumb you can think of it as the following: UAT is the QA for people who request the software to make sure the request is fulfilled. QA team is usually more technical and can troubleshoot issues that go past the enhancement request and how it affects the system overall. This may involve 3rd party data warehousing, reporting, communication ...



Only top voted, non community-wiki answers of a minimum length are eligible