Along the same lines, it might be useful to compare testing methodlogies- without publishing War and Peace, can you who are willing summarize your testing? I think we can all learn from others, and improve our testing processes to reduce unplanned "oops" outages.
For example, I know of a site that had a testing methodology similar to this: 1. Development (coding changes) followed by unit testing in a development region (batch programs in the developer's personal library. Minor regression testing of inter-related components here. 2. Migration to a test environment - integration testing of the changes in the related components and regression testing of the application. Then full case (all possibilities covered by the change) and stress testing here. All this done by the development/support team. 3. After documentation, report and screen presentation sign off by user, creation of parallel "integration/QA" environment, using live production data for QA and UAT, conducted by user team/user management. This is a temporary, throw-away environment. 4. Finally, migration to the production environment with final UAT and signoff conducted during an application or system outage window. This is conducted by select users (sometimes the entire user team) and user management, with the developer/developer's manager available for last minute training or usage questions. Data is sometimes preserved via backups, with "live" processing, and subsequent restore of data, or in some cases, live processing is conducted during this test and left in place. * Don * On Tue, Jun 15, 2010 at 9:49 AM, George Henke <[email protected]> wrote: > Would someone please tell me what is "best practices" as to where most of > the User Acceptance Testing (UAT) should take place? > > 1) In the developers' Integration Testing environment and conducted by > developers > 2) In the Quality Assuarnce (QA) environment and conducted by QA analysts > Also where should final user signoff occur? > > Thank you > > George Henke > (C) 845 401 5614 > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
