Test/QA Process

  1. Get QA involved during project estimating.

  2. Prior to development starting, break project into mini-deliverables that can be published and QA’ed.

  3. QA develops test plans and reviews with SL developer and/or the Project Manager.

  4. Developers do incremental releases to contractor environment and QA tests earlier on in the process.

  5. Once code is feature complete, SL (QA/Dev/PM) sets up a review meeting with client to demo features, QA not completed at this point, but get buy-in on functionality.

  6. QA does their complete testing in the test contractor environment, once it is completed, we have the client publish to their environment in test.

  7. QA completes testing in client test environment.

  8. Client publishes to their staging environment.

  9. QA completes testing in their staging environment.

  10. QA publishes and adds to Client Reference Materials (GSP – add in Version One Ticket and add a comment to ensure all are notified), a “QA Packet” that shows what was tested, includes screen shots as appropriate.

  11. QA Packet Includes: *Requirements Documents and/or V1 Tickets and/or PDF mock-ups from Client *Completed QA Tests & Plan

  12. Client publishes to production.

  13. SL QA does a “smoke-test” for general functionality.