Configuration Files
Most of the configurable settings in AutoQA are well documented in the comments of the configuration files.
- General Configuration Settings
- autoqa.conf
- Yum repos used by AutoQA
- repoinfo.conf
- FAS credentials used by AutoQA
- fas.conf
Bodhi Comment Email Settings
Some of the settings used to configure the behavior of emails sent when Bodhi comments are sent by AutoQA require a bit more explanation than what is contained in autoqa.conf.
States
The possible states of a test or an update as used here are PASS, FAIL, INCOMPLETE or NOTRUN.
Test State Change
A single test can change state that may or may not affect the update state as a whole. An example of this would be an updated package that changes test results from FAIL to PASS.
Update State Change
This type of state change is when the update as a whole would change from PASS to FAIL or FAIL to PASS.
Example where overall result changes from FAIL to PASS:
| Run | Test Result | Overall Result | ||
|---|---|---|---|---|
| depcheck 32bit | depcheck 64bit | upgradepath | ||
| Previous | PASS | PASS | FAIL | FAIL |
| Current | PASS | PASS | PASS | PASS |
Example where overall result does not change:
| Run | Test Result | Overall Result | ||
|---|---|---|---|---|
| depcheck 32bit | depcheck 64bit | upgradepath | ||
| Previous | PASS | FAIL | FAIL | FAIL |
| Current | PASS | FAIL | PASS | FAIL |
Koji Tags and Expected Tests
Since upgradepath is only run on packages in updates or updates-pending, it isn't run on packages in updates-testing. This means that the expected tests change depending on how packages are tagged.