[AutoQA] #352: Determine AutoQA Functional Self Test Cases
#352: Determine AutoQA Functional Self Test Cases
--------------------+-------------------------------------------------------
Reporter: tflink | Owner:
Type: task | Status: new
Priority: major | Milestone: Self Test
Component: core | Keywords:
--------------------+-------------------------------------------------------
In order to start forming a better self test suite for AutoQA, we need to
start cataloging situations that will make for good functional regression
tests.
Instead of focusing on how to get them all run, the idea is to describe
the situations that would make for good tests. Formatting and categorizing
the tests will be left for another ticket.
Examples of jobs that have caused problems in the past or continue to
cause strange problems would be helpful.
An extremely simplistic example for depcheck might look like:
=== Package Descriptions ===
|| '''Package''' || '''Depends On''' ||
|| foo-1.0-1 || bar-1.0-1 ||
|| foo-2.0-1 || bar-2.0-1 ||
=== Repo Contents ===
|| '''Name''' || '''Packages''' ||
|| stable || foo-1.0-1, bar-1.0-1 ||
|| pending || foo-2.0-1 ||
=== Expected Results ===
Failure because foo-2.0-1 depends on bar-2.0-1 which is not available.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/352>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project