This question has been flagged
1 Reply
4748 Views
testarchitectureproductionqa
Avatar
Sandi Langley

I'm open to learning new things, but I gotta tell ya', I'm struggling with this one!  Could someone please explain the system architecture to me in a way that I can be convinced to give up my old-school paradigm?  I have always made changes in one instance (DEV) and then, after unit testing, migrated my changes to a pristine copy of production (TST) where integration testing was performed. If the changes passed QA/UAT in TST, then they were migrated to production (PRD).

We branched off from PRD more than a month ago into what is being called "TST". Our current environment no longer resembles PRD because we have been experimenting as we try to find solutions.  Odoo suggests that we transport directly from TST to PRD.

1.  The processes are not working in TST due to a configuration error that nobody wants to find or fix.  Bottom line: it doesn't work.

2.  The changes have not ever been tested in an environment that looks like PRD.  I don't know if it will work there or not.

Please help a sister out!  Are you guys using a 2- or 3-tier system?  What have you seen to be the advantages and/or disadvantages of your approach?

Avatar
Discard
Avatar
Paresh Wagh
Best Answer

Hi Sandi:

You have already covered the key points.

There are typically 2 approaches that are widely adopted:

  1. DEV => TEST/UAT => PROD

  2. DEV => TEST => UAT => PROD

Approach 2 is typically used when you have multiple teams working on the same system. The difference between 1 and 2 is that TEST is used by the development team for "integration" testing (changes made to different modules) whereas UAT is used by the power users for "user acceptance" testing.

In both approaches, it is recommended that TEST/UAT should be a replica of PROD with obfuscated data, if possible, so that you know for sure that the changes made will finally work as expected in PROD.

Hope that helps.

Avatar
Discard