-1

I have three distinct environments: test, QA, and prod. Test and QA share the same database but have different front-ends. This means there can be UI changes in the test environment that are not present in QA. What should be the testing stategy in such scenario? Should a full test be conducted in the test environment when a front-end change is made, and then only a smoke test in QA? Or vice versa? Or should a full test be conducted in both environments?

Additionally, what happens if there is a backend change, such as adding a column to a table? How should the testing strategy be adjusted?

3
  • What is the difference between "test" and "QA"? Why do two of your environments share a database?
    – Thomas Owens
    Apr 2 at 10:27
  • Imo such a setup with a shared database can only work if you ensure test and qa run the same software version at all times. If you need separate test and qa environments, go all the way and give them their own database.
    – Rik D
    Apr 2 at 16:15
  • 1
    don't have a shared database?
    – Ewan
    Apr 2 at 21:22

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Browse other questions tagged or ask your own question.