QA:Package Update Acceptance Test Plan
The purpose of this document is to present a set of rules that determine whether a package update is considered ACCEPTED (i.e. it is ready to be committed to repository), REJECTED (i.e. the build should be discarded and a fix should be requested) or NEEDS_INSPECTION (i.e. similar to REJECTED at the moment, but it becomes ACCEPTED if all errors are waived).
The test plan is divided into three main sections:
- Mandatory tests
- Introspection tests
- Advisory tests
All tests are executed in arbitrary order. If any of available tests fails, other tests still continue to be executed.
This test plan contains only tests that can be automated, i.e. executed without human intervention. No manual tests will be performed. (But this does not reject human intervention when inspecting the test results, like waiving false errors.)
Test Pass/Fail Criteria
All mandatory tests must pass. If some of mandatory tests fail then the package update is considered REJECTED.
All introspection tests must pass. If some of introspection tests fails, the package is considered NEEDS_INSPECTION (provided that all mandatory tests passed, otherwise it stays REJECTED). An eligible person may inspect errors of a failed introspection test and waive them.
The package update is considered ACCEPTED when:
- all mandatory and introspection tests have finished cleanly (not crashed or otherwise aborted)
- there are no failed mandatory tests
- all failed introspection tests are waived
The results of advisory tests have no impact on package update acceptance.
- A decision if a particular package update has been ACCEPTED, REJECTED or NEEDS_INSPECTION.
- A full log of individual test cases' output containing infos, errors or warnings.
- A special output marked as informative from any test case that passed but wants to convey additional information.
- Any test scripts used for automation or verification.
Note: More tests are going to be added in the future (manpage test, desktop-file test, etc).
- Package sanity - must be installable, uninstallable, upgradeable, etc
- Depcheck - the update must not break dependencies of other packages
- Conflicts - there must be no file/package conflicts
- Upgrade path - the update must not break upgrade path
- AutoQA (the automated test execution framework) must be packaged and deployed in Fedora infrastructure. It will be used for test execution.
- Test cases will be executed on all hardware platforms relevant for that particular package build. The only exception being test cases which can be executed in a platform-neutral way.
- The test cases should strive for testing updates in such a way that is as close as possible to regular update process for the end-user. That means that generally the system should be fully up to date from 'fedora' and 'updates' repositories before running the test case. Also if there is a whole set of pending updates that are going to be accepted and pushed to stable repositories together, the testing should consider that set as a whole, not just individual packages in it.
Responsibilities and permissions
- Quality Assurance team members are responsible for executing this test plan.
- Introspection tests failures may be waived by:
- package maintainer
- package update builder
- update ticket author
- It is the responsibility of the waiver to ensure that he/she waives only false errors, not real problems.
- When all introspection tests failures are waived, the state change from NEEDS_INSPECTION to ACCEPTED is to be handled automatically by Quality Assurance team tools.
- Groups of people that are allowed to waive errors may also re-execute the test plan on a particular package.
This test plan is executed on every package update or new package build that is submitted to 'updates-testing' or 'updates' repository through Fedora Updates.