QA process for Business Catalyst projects.

Starting a project What QA needs to start testing::  Specifications – A detailed description of the product, with all the products boundaries and details specified.  Test Environment – A mirror of production where code can be placed and tested without affecting production data.  Code – Code to be tested before release, should be complete and looked over by developer.  Database and task changes – Changes should be made to the QA environment before testing starts. This includes DB schema changes and scheduled task changes.

QA Pre-Test Prep Work 1. Test Plan - Documents the strategy that will be used to verify and ensure that a product or system meets its design specifications and other requirements. 2. Test Cases – Tests created from specifications. 3. Trac Milestone - The milestone will be a place holder for any bugs or enhancements found in the project.

Testing the Project 1. Execute test cases - Go through each test case created from specifications in TestLink. 2. Corner cases – While testing corner case come up. These test cases need to be added to TestLink when they are found. 3. Database changes – Test out any changes to DB schema. 4. Logging Bugs – Bugs should be logged into Trac, with steps to reproduce. Bugs should be assigned to the original developer. 5. Automation – Create automated tests using Selenium that can be ran when product is released to production.

Project sign off 1. Test cases – Test cases must pass. All test case statuses must be updated in TestLink. 2. Trac Tickets – All P1 and P2 must be verified and close by QA. 3. Automation – Automated tests should be finished and ready to run when project goes live. 4. Deployment Plan – A deployment plan should be created informing Ops what needs to happen in order to have a successful release. This should include the code, DB changes, and any scheduled jobs that need to be ran before release.