#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.
#352: Create AutoQA Functional Self Test Cases --------------------+------------------------------------------------------- Reporter: tflink | Owner: Type: task | Status: new Priority: minor | Milestone: 0.6.0 Component: core | Resolution: Keywords: | --------------------+------------------------------------------------------- Changes (by tflink):
* priority: major => minor * summary: Determine AutoQA Functional Self Test Cases => Create AutoQA Functional Self Test Cases * milestone: Self Test => 0.6.0
Old description:
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.
New description:
== Description == In order to start running functional self tests, we need to have tests to run.
There are two parts of this: 1. Determine the format to write the tests in 1. Write the tests
== Dependencies == There is a hard dependency on #355 (Determine use cases for functional self tests)
This is related to #352 (Create AutoQA Functional Test Cases) and will likely be worked on in tandem.
Comment:
Modifying ticket contents to match with discussion during 0.6.0 planning meeting.
Changing priority and milestone to match NTH for 0.6.0
#352: Create AutoQA Functional Self Test Cases --------------------+------------------------------------------------------- Reporter: tflink | Owner: Type: task | Status: new Priority: minor | Milestone: Self Test Component: core | Resolution: Keywords: | --------------------+------------------------------------------------------- Changes (by kparal):
* milestone: 0.6.0 => Self Test
autoqa-devel@lists.fedorahosted.org
-
fedora-badges