From Fedora Project Wiki

(Test Strategy)
(Test Strategy)
Line 7: Line 7:
 
* Serve as a base for the test planning for future Fedora 12 releases
 
* Serve as a base for the test planning for future Fedora 12 releases
 
== Test Strategy ==
 
== Test Strategy ==
Fedora QA project organizes testing of software as it is released into Rawhide, updates-testing, or as it appears in a supported public release.We will announce [https://fedoraproject.org/wiki/QA/Test_Days/F12  test day] in [https://www.redhat.com/mailman/listinfo/fedora-test-list fedora-test-list] and organize to run [https://fedoraproject.org/wiki/QA/Test_Days/F12  test day] to co-ordinate focused testing on a specific feature or component in community. These tests include manual or automatic testing.After testing,we will work with developers to fix and close bugs. If you'd like to help making Fedora better,please join us in  [https://fedoraproject.org/wiki/QA/Test_Days/F12  test day] or [https://fedoraproject.org/wiki/QA/Join other Fedora QA activities]
+
*Fedora QA project organizes testing of software as it is released into Rawhide, updates-testing, or as it appears in a supported public release.We will announce [https://fedoraproject.org/wiki/QA/Test_Days/F12  test day] in [https://www.redhat.com/mailman/listinfo/fedora-test-list fedora-test-list] and organize to run [https://fedoraproject.org/wiki/QA/Test_Days/F12  test day] to co-ordinate focused testing on a specific feature or component in community. These tests include manual or automatic testing.
 +
*Fedora QA project tracks test results against Fedora 12 milestone Release Candidate builds.Fedora 12 milestones can be found at [[Releases/12/Schedule]].
 +
*After testing,we will work with developers to fix,close bugs and give corresponding feedback. If you'd like to help making Fedora better,please join us in  [https://fedoraproject.org/wiki/QA/Test_Days/F12  test day] or [https://fedoraproject.org/wiki/QA/Join other Fedora QA activities]
  
 
= New features of {{FedoraVersion|long|12}} =
 
= New features of {{FedoraVersion|long|12}} =

Revision as of 05:51, 11 June 2009

Introduction

This document describes the tests that will be created and used to verify the installation of Fedora 12.

The goals of this plan are to:

  • Organize the test effort
  • Communicate the planned tests to all relevant stake-holders for their input and approval
  • Serve as a base for the test planning for future Fedora 12 releases

Test Strategy

  • Fedora QA project organizes testing of software as it is released into Rawhide, updates-testing, or as it appears in a supported public release.We will announce test day in fedora-test-list and organize to run test day to co-ordinate focused testing on a specific feature or component in community. These tests include manual or automatic testing.
  • Fedora QA project tracks test results against Fedora 12 milestone Release Candidate builds.Fedora 12 milestones can be found at Releases/12/Schedule.
  • After testing,we will work with developers to fix,close bugs and give corresponding feedback. If you'd like to help making Fedora better,please join us in test day or other Fedora QA activities

New features of Fedora 12

Important.png
FIXME
Need confirmation on the following list of features for Fedora 12

The following list of features was obtained from Anaconda/Features. Test plans for these features will be designed/developed on each feature page.

Schedule/Milestones

  • The Fedora 12 release schedule is available at Releases/12/Schedule
  • Each major milestone will demand a full regression run (Alpha, Beta, Preview Release)

Community Testing

The Fedora 12 test day is available at QA/Test_Days/F12

Test Environment/Configs

For Fedora 12, we will execute test cases on these hardware platforms:

  • i386
  • ppc
  • x86_64

Test Cases/Priority

  • Test cases for Fedora 12 ,please refer to QA:Fedora_12_Install_Results_Template#Test_Areas
  • This test plan will use priority of 3 level for test cases
    • level 1 is intended to verify that installation is possible on common hardware using common use cases.
    • level 2 takes a step further to include more use cases.
    • level 3 captures the remaining identified use cases

Reporting Bugs and Debugging Problems

Communicate

If you want to participate test day of Fedora 12,you can get help or give feedback by any of these ways:

References