Best Practices - Testing

Testing

Testing is an important and vital step in the building and deployment of any site. Testing must be done at all levels; the technology team, client manager, and the client.  Testing helps to ensure WPG brings to its clients a high quality functioning site. 

Here is what you should expect at each level of testing:
 
Round 1.  Development QA. The technology team tests any new code and its effects on the system; in addition to testing the new updates to the database. This process ends with a notification from technology team of site being completed or of changes being completed in the staging or pre-production environment
 
Round 2. Final QA. The Client Manager reviews the site documentation, ensures any requested changes have been completed and establishes test cases for specific logins so all possible scenarios in the flow can be tested.
 
To test a site the Client Manager logs in to the staging site using the appropriate credentials. If the Client Manager is testing changes to an existing site the starting point is to begin where the change was made.  The change needs to be confirmed and if it is part of a work flow all parts that touch that flow need to be tested to ensure that the site is still functioning properly. If the site is new this requires testing every link on every page, checking all flows entirely from start to finish and checking all wording.  The manager tests the Forgot Password link, the Customer Support email and phone support lines, Confirmation and Cancellation notices to be sure all are functioning as expected.
 
If the Client Manager finds items that are not completed or functioning as expected the product goes back to the technology team to address outstanding issues.  When notified that the issues have been resolved the manager runs through all the testing again.  When satisfied the Client Manager notifies the client that the site or changes to the site have been completed and are ready for review in staging environment. The Client Manager provides the Client with all credentials necessary for testing.
 
Round 3.  Client Review. The Client logs in to the staging site with the appropriate credentials and reviews the site for look and feel. If you are testing changes to an existing site go to each of the changes you requested and confirm the changes are complete and functioning as you expected. If you are testing a completely new site test every link on every page, checking all flows entirely from start to finish and checking all wording. Confirm the Forgot Password link, the Customer Support email and phone support lines, Confirmation and Cancellation notices are all are functioning as you expected. Any errors revealed in testing should be detailed and referred back to the Client Manager. Testing any fixes resumes at Round 1.
 

Finally, either thru a sign-off document or directly worded email the Client provides the Client Manager permission to move the site or changes to the production environment.
 
Once the Client Manager has approval from the Client, the technology team is notified and a schedule is put in place to move the site and/or changes to the production environment.  For new or seasonal sites there is a go-live checklist that is completed as the site is taken live.  The checklist is completed by the client manager and the technology team and includes a limited number of testcases. When the checklist is complete the Client Manager notifies the Client that the site is live or that changes made to an existing site have been moved to the production environment.