|
QUALITY ASSURANCE
What is your commitment to quality? How do you
measure that commitment?
It is our commitment to deliver services and products that exceed
our client's expectations. We have several metrics that represent
several aspects of client quality:
Budget - budget deviation throughout projectSchedule - schedule
deviation, timeliness, response time, performance to SLA
Requirements - completeness, stability
Productivity -size/effort, review and test effectiveness
Product Quality - defect rate, quality cost, defect removal efficiency
What tools are used for developing test plans, automated testing,
and for tracking issues?
Test plans are developed from the functional requirements/use cases.
Test scripts are developed and automated, if appropriate. Issues/defects
are reported using a defect tracking system that is shared by Agilis
Solutions Portland, our OSDC, and our client. The defect tracking
system we use, by default, is StarTeam. If requested by the client,
we can use the client's defect-tracking system.
How does QA communicate with the developers?
Issues/defects are formally communicated to the developers through
the defect-tracking system. Specific instructions and/or test cases
are provided to ensure the defect can be re-created or that the
issue is understood. The developers respond with a resolution through
the defect-tracking system.
Does your staff utilize unit tests? If so, how are unit tests
performed? Are these developed and executed by the developer or
by QA?
Unit tests are developed for every application. They are performed
after every build. They are developed and executed by the developers.
However, QA reviews the unit test plans, the unit tests themselves,
and the unit test results to ensure they meet specs and standards.
Does the QA staff read source code as part of their testing process?
The QA staff participates in code reviews on a periodic basis. However,
during testing, they are not required to read source code as part
of their testing process.
|
