Quality Assurance Testing
Our QA testing process is adapted to meet the unique requirements of each project. Our standard process incorporates the following key elements.
The quality assurance team starts by developing, in consultation with the project manager a Test Plan based on detailed specifications outlined in the FRD. The test plan is a high level summary that describes the areas that we will test, and how we will test them. The test plan also outlines the scenario tests that will be conducted to model how the user will interact with the key functional areas the site.
Each stage in the testing process is documented in a Test Script. Test scripts describe and document each step in the testing process, what was tested, and by whom and what the results of the test were. Test scripts are customized to meet the needs of each project and most projects have a series of test scripts. A typical test script would be documented in a spreadsheet or database and for each step would record the objective, description of tester action, results, and record any bugs found. As well, the test script would also record the name of the tester, the test configuration, date, and build number tested, if applicable.
Test Tracking and Bug Reports
Any bugs found during the testing process are recorded documented on our web-based bug tracking system.
Our tracking system assigns a tracking number, and records the date the bug was found and reported, and who the
bug is assigned to. The tester who records the bug is able to describe the bug, and the steps to reproduce it,
designate a priority and category to it, and assign responsibility for fixing the bug to the appropriate team member.
Using the bug-tracking tool, the development and testing team members can communicate efficiently online regarding
the bug and their comments, queries and clarifications documented with the bug. Each step in the process is transparent
and documented, and the project manager can monitor the progress for all open bugs easily online and act to keep the
project on schedule.
Bugs are fixed and posted to the test server by the appropriate programmer, and the test team is notified
that the bug has been fixed. The bug is assigned back to the test team for retesting and verification.
A bug is not closed until the fix has been checked and verified by the testing team. The system allows us
to monitor and track the progress of Quality Assurance testing,
and to assure each bug is fixed and closed before the end of the testing process.
At the end of the project, the QA team lead provides a testing report that includes an overview of the
test results as well as all documentation gathered during the testing process. Together the report and test
documentation provide valuable feedback to our development and testing teams,
giving them the information they need to continually improve their process.
For more information about web standards and our services in these areas, please contact, Anne Louise Currie at 416-410-5726 or by email at firstname.lastname@example.org