QA Table of Contents

The purpose of this page is to serve as a repository for all information about the Quality Assurance department.  This includes processes, Best Practices and links to commonly used resources.

The Quality Team's primary goals are:

• Evaluate Pentaho Software and be able to provide the following statistics (Product Owners will use these statistics to determine if the RC software is valid for release):

  • Known unresolved defects

  • Test coverage percentage for areas covered by test cases (i.e. 50% of dashboards functionality is covered by test cases)

  • Test coverage percentage for configurations covered by test cases and test plans (i.e. 80% of the supported configurations have been fully tested, 10% have been partially tested, 10% have not been tested)

  • Test execution percentage and status for the test plan execution (i.e. 80% of the test plan has been executed - the outstanding areas are ...)

  • Known risks / gaps that will cause measurement inaccuracies

• Evaluate Pentaho software during development to identify new defects / regressions based on current development

  • Tracking new development and identify impact to existing test cases

  • Perform periodic regression measurements to quickly identify newly created defects during development

• Tracking incoming defect reports and identify potential updates to test cases / future test plans

  • Determine if the defects should have been captured with previous testing effort and identify gaps if so

  • Determine what update to the test cases / test plan should be made (if any)