Quality Assurance - Purpose & Client Strategy

[Former Member]

Hello,

Originally, it was explained to us as a best practice to set up a QA system that would closely mimick production. One productive client in production would mean one productive client in QA.

Furthermore, the original intent of QA was to be used to perform an end-to-end test of a "fully" delivered solution (say as close to done as reasonable) when used for projects. It was not architected to handle a high degree of change that would come from a solution that may be 30-50% delivered for example (risks of frequent re-start etc).

We are receiving challenges to the original approach to QA, and I would like to understand how you are handling your QA system, it's client strategy, and it's purpose. Your insight would be very much appreciated.

Thank you,

John

Edited by: John Klaassen on Mar 18, 2008 8:22 PM

[Former Member]

This message was moderated.

[JPReyes]

A QA system is as its name suggest a "Quality Assurance" System... meaning that you test your developments in a scenario as close to produccion as posible (if not exact) so you don't risk sending faulty code to the live environment...

Client strategy is up to customer specification some (most) companies have one client as replica of production an other companies have different scenarios to replicate separate projects or developments, also is very common that some companies use QA clients as training environments.

Hope this helps

Juan