This ticket also depends on https://pagure.io/taskotron/task-upgradepath/issue/1

This issue depended on a ticket not moved from Phabricator.
T17: extract upgradepath and depcheck from autoqa so that they can run standalone

Since depcheck and upgradepath are so tightly coupled with AutoQA, they don't run well outside of that environment. Extract the core logic of those tests so that the functional tests can be written outside of AutoQA

This issue depended on a ticket not moved from Phabricator.
T16: generate specially crafted rpms to induce failure and passing in depcheck

As a functional test of depcheck, create a set of rpms (they don't have to be real, rpmfluff is fine) which implement the scenarios described in the output of #12. See T13 for a list of situations.

It may be wise to implement a meta-language using YAML or something similar to generate rpms and repos based on contents of a file.

This issue depended on a ticket not moved from Phabricator.
T15: generate list of situations in which upgradepath should pass and fail

Similar to T13, we need to come up with a relatively-comprehensive list of the situations in which upgradepath should pass and situations in which it should fail.

This issue depended on a ticket not moved from Phabricator.
T13: Create list of situations in which depcheck should pass and fail

[[ http://fedoraproject.org/wiki/AutoQA_tests/Depcheck | Depcheck ]] is a complicated check that looks for dependency issues in incoming packages before they are pushed to the stable repos.

An initial list of scenarios (in terms of "should pass" and "should fail") are available on the fedora wiki: https://fedoraproject.org/wiki/User:Tflink/depcheck_scenarios