From Fedora Project Wiki

Line 8: Line 8:
  
 
Spin Maintainers should also verify the changes they make to make the Spin unique actually work, as well as create a new test case (using [[QA/TestCases/TestCaseTemplate]]) for every item that needs to be tested by the Quality Assurance Team.
 
Spin Maintainers should also verify the changes they make to make the Spin unique actually work, as well as create a new test case (using [[QA/TestCases/TestCaseTemplate]]) for every item that needs to be tested by the Quality Assurance Team.
 +
 +
== Daily Compose Testing ==
 +
 +
The Spin SIG can run daily compose testing for spins already in the spin-kickstarts GIT repository.

Revision as of 20:49, 11 January 2009

Spin Tests

The ever growing amount of Test Cases lives in. This list comes from the Quality Assurance Team, and may be extended with help of the Spins SIG, the Spin Maintainers whenever a new test case is created.

What tests should Spin Maintainers run?

Spin Maintainers should run these tests regularly. The Spins SIG expects these tests to be ran on a monthly basis, to enable fixes to go through before the next test run, and to enable errors to be detected in time. The Spin Maintainers should definitely send reports on these tests to the Spins SIG, via the fedora-spins -at- lists.fedoraproject.org mailing list.

Spin Maintainers should also verify the changes they make to make the Spin unique actually work, as well as create a new test case (using QA/TestCases/TestCaseTemplate) for every item that needs to be tested by the Quality Assurance Team.

Daily Compose Testing

The Spin SIG can run daily compose testing for spins already in the spin-kickstarts GIT repository.