Our testing process consists of the following stages: Investigation, Planning, Testing, Release.
Investigation
During the Investigation stage our specialists study the product that should be tested.
Planning
During the Planning stage the Test Lead assigned to your project develops the Test Plan for the future project activities. This document provides information on requirements, strategy, environment(s), resources, schedule, deliverables and a preliminary list of tests to be performed. The Test Plan is reviewed by our Test Manager and submitted to you for approval.
The Test Plan describes:
the scope of testing in terms of the software features to be tested
the approach to testing in terms of testing methods, tasks and deliverables
testing logistics in terms of schedules, resource requirements and individual responsibilities.
It identifies the items and features to be tested, the testing tasks, the personnel responsible for each task, and the risks associated with this plan.
The Test Plan helps to:
Organize the technical aspects of software testing.
Establish an appropriate communication flow
Make estimations and evaluations
Guarantee product full testing coverage
Improve the testing process on the basis of Test Plan reviews, submitted by the team and customer
Estimate the amount of planned testing
Provide other stakeholders with information on the test activities
Assign tasks
Track the testing process
When the Test Plan is accepted, the Test Lead and senior test engineers draft the final list of test procedures and combine them in the Test Matrix (a document that shows the current progress status of test activities). The Test Manager reviews and approves the list. The estimations are updated on the basis of the Test Matrix.
Testing Testing - at this stage the test team has the primary task to carry out the scheduled Test Procedures and identify the flaws. In addition, they help repair the identified bugs. The Test Team Leader is responsible for all formal test activities. He/she manages the bug database, tracks and reports on the test progress, develops automated tests, discusses with customer the identified problems (in form of bugtfests (regular meetings between customer and test team to review the priority and status of reported bugs) or in another form, as requested by the customer) and informs the customer about the current progress status.
These reports include:
Current bug status as per the bug database (number of opened, closed, test review, etc.)
Statistics on new bugs found over a given period (including their Urgency and Severity)
Statistics on bugs closed over a given period
Graphs and tables displaying the above statistics.
The weekly test reports contain the following additional information:
Builds tested over a given period of time
Total number of test procedures
Test procedures attempted
Test procedures blocked
Test procedures successfully run
Also, the Test Team Leader reports on the following matters as they arise during the test cycle:
Bugs Blocking Test procedures
Missing Features
Problematic Features
The Test Engineers are responsible for setting up environment on all test machines, running all Test Procedures as directed by the Test Team Leader, and capturing all Test Procedure activity into a test procedure script. They are also responsible for entering all bugs into the database properly and performing test verification of fixed defects.
Release Release - at the beginning of this stage the Test Team Leader develops the Release Plan to provide the customer with a list of outstanding issues that might hinder the product release. As development fixes the bugs, test engineers perform verification of fixes and potentially affected product areas, the Test Team Leader tracks the progress of this process in the Release Plan.
When all bugs are fixed, the test team performs the acceptance testing to make sure that no additional problem was introduced during the repair stage. Certain problems, identified during the acceptance testing are regarded as "show stoppers". In such cases, the respective problems must be fixed in controllable way and the acceptance testing (or a part of it) must be re-run. Though the "show stopper" process is rather an exception than a rule, it should be considered as a possible situation. If the acceptance tests are successfully run, then product is ready for release.
The Release Authorization form details the performed tests and their results. Any software quality metrics (if requested by the customer) is included in this document.
We may also advise you on what features could be changed or added to improve the quality of your products for future releases.
Member login
The latest project
SQA Partners is currently testing it's own product Webmatrix
Estonian Address: Tallinn, Harjumaa, Estonia, Laki 19, 12915
Ireland Address: 14 Mellifont Avenue, Dun Laoghaire, Dublin, Ireland
