 |
“Beta
Breakers helped Schoolpop out with an urgent QA job, given absolutely
no notice. We called them on Friday, they wrote the test plan over the
weekend, and were testing on Monday.
They did an excellent job of testing our application both functionally
and on all of the operating system and browser versions we support. Beta
Breakers was reasonably priced, responsive, flexible, and there when we
needed them to help get our product ready for release.
The Beta Breakers people we worked with were very competent and were fun
to work with. We look forward to working with Beta Breakers again, whenever
we need additional QA resources, or when we need a more extensive lab
testing environment.”
Schoolpop
|
|
|
It's great that your product is new and cool,
but does it actually work? From basic commands to clean audio and video,
from graphics to grammar, everything must function perfectly.
Perhaps your development team tells you that the product is stable –
that it functions perfectly and according to specifications. They tell
you they are confident because they tested it themselves. Do not be lulled
into a false sense of security. Whereas your development team has the
best of intentions, history has demonstrated that many dev teams are just
too close to the product to provide objective and effective quality assurance.
You owe it to yourself to hire a competent, reliable and independent quality
assurance firm to lend a fresh pair of eyes to the project.
Bring Beta
Breakers on board and we will clearly demonstrate a level of professionalism
and competence resulting in the discovery of functionality issues that you never knew existed.
We will track them using our own proprietary, secure, online bugbase called
BetaBugs and give all members of your dev team access.
Purpose
The purpose of functionality testing is to reveal issues concerning
the product’s functionality and conformance to stated/documented
behavior.
Methodology
The first step in evaluating a program’s functionality is to
become familiar with the program itself, and with the program’s
desired behavior. Ideally, this process is aided by documentation
such as the program’s functional specification or user manual.
Even without such documentation, expected behavior can often be adequately
modeled based on industry standard and tester intuition. Once a program’s
expected functionality has been defined, test cases or test procedures
can be created that exercise the program in order to test actual behavior
against expected behavior. Testing the program’s functionality
then involves the execution of any test cases that have been created,
as well as subjecting the program to a certain amount of ad hoc testing
– this is testing that is not rigorously structured, but instead
attempts to address areas that the tester, using his/her experience,
feels are high risk areas, and usually involves exercising the program
in an unconventional manner. Certain portions of a functionality testing
effort can also be automated, but this depends on several factors,
and should be discussed with a qualified Beta Breakers engineer.
|
Finally, it is extremely important to note that
whereas many QA labs are just a “point-and-click house”, we
are far from it. Beta Breakers is a strategic product development partner
that is completely involved in every aspect of your project and is committed
to testing every last detail no matter how small. We understand what is
at stake and we know what to look for.
|
|
