 |
“Beta
Breakers did an excellent job in testing our web-based training courses.
They are well equipped with professional staff and the best practices.”
Peoplesoft
“Beta Breakers offers Roundpeg what we need when it comes to an outsourced partner – flexibility and competence. Their staff has always exhibited a comprehensive and professional service to our clients.”
Roundpeg
|
|
|
Sometimes one step forward turns into two steps
back. We know that in the world of software development. Solutions originally
intended to fix problems can create new and potentially more serious problems.
Enter regression testing. This discipline enables us to track issues,
check the effectiveness of a solution, and detect any new issues which
may have been created as a result of fixing the original problem. Reports
are generated, problems are tracked, and the process continues until all
of the issues are solved or a new version is developed.
Key to the careful tracking of issues is BetaBugs.
Our homegrown, online bug tracking software is available to you and your
staff 24 hours a day, seven days a week. It is absolutely secure and very
easy to use. With BetaBugs, all people involved in the quality assurance
process will have access to the latest outstanding issues thereby gauging
progress every step of the way. As the regression phase of the QA cycle
continues, regular updates to BetaBugs help coordinate the efforts of
both the development and QA teams.
Purpose
The purpose of regression testing is to ensure that previously detected
and fixed issues really are fixed, they do not reappear, and new issues
are not introduced into the program as a result of the changes made
to fix the issues.
Methodology
Typically Beta Breakers performs regression testing on a daily basis.
Once an issue in the defect tracking database has been fixed it is
reassigned back to Beta Breakers for final resolution. Beta Breakers
can either reopen the issue, if it has not been satisfactorily addressed,
or close the issue if it has, indeed, been fixed. For more involved
projects lasting several months, several full regression passes may
be scheduled in addition to the continuous regression testing mentioned
above. Full regression passes involve re-verifying all closed issues
in the defect tracking database as truly closed. A full regression
pass is also typically performed at the very end of the testing effort
as part of a final acceptance test. In addition to verifying closed
issues, regression testing seeks to verify that changes made to fix
known defects do not cause further defects. Beta Breakers can produce
a regression testing suite consisting of test cases that evaluate
the stability of all modules of the software product. Quite often,
automation of this regression testing suite is well worth considering. |
If you wish to gain access to a sample bugbase
within BetaBugs, please contact us with
your request.
|
|
