From Fedora Project Wiki

< QA

m (Added links)
(Updated for Fedora 11 schedule)
Line 5: Line 5:
== When are Test Days? ==
== When are Test Days? ==


Test Days occur every Thursday between the Alpha and GA milestones of a Fedora release.   
Test Days occur every ''Thursday'' between the Alpha and GA milestones of a Fedora release.   


For a list of previous and planned test day topics, see the table below:
The Test Day schedule for previous releases is available at:
* [[QA/Test Days/F10|Fedora 10]]
 
For a list of planned test day topics, see below.


{|
{|
! Date !! Topic(s)
! Date !! Topic(s)
|+align="bottom"|See [[Releases/10/Schedule|F10 schedule]] and [[Releases/10/FeatureList|F10 features]]
|+align="bottom"|See [[Releases/11/Schedule|F11 schedule]] and [[Releases/11/FeatureList|F11 features]]
|- style="background-color:#def3fe;"
| 2009-01-20 || Alpha Freeze
|-
| [[QA/Test Days/2009-01-20|2009-01-22]] || Open Slot
|-
|-
| [[QA/Test Days/2008-08-14|2008-08-14]] || [[Anaconda/Features/EncryptedBlockDevices|EncryptedBlock Devices]] and [[Features/BetterStartup|Plymouth]]
| [[QA/Test Days/2009-01-29|2009-01-29]] || Open Slot
|- style="background-color:#def3fe;"
| 2009-02-03 || Alpha Release
|-
|-
| [[QA/Test Days/2008-08-21|2008-08-21]] || Postponed (see [https://www.redhat.com/archives/fedora-test-list/2008-August/msg00318.html fedora-test-list])
| [[QA/Test Days/2009-02-05|2009-02-05]] || Open Slot
|-
|-
| [[QA/Test Days/2008-08-28|2008-08-28]] || [[Features/BetterPrinting|BetterPrinting]] and [[Features/ApplianceTools|ApplianceTools]]
| [[QA/Test Days/2009-02-12|2009-02-12]] || Open Slot
|-
|-
| [[QA/Test Days/2008-09-04|2008-09-04]] || [[Anaconda/Features/SaveToBugzilla|Save to Bugzilla]] and [[Features/ConnectionSharing|Connection Sharing]]
| [[QA/Test Days/2009-02-19|2009-02-19]] || Open Slot
|-
|-
| [[QA/Test Days/2008-09-11|2008-09-11]] || [[Features/VirtStorage|Virtual Storage]] and [[Features/VirtRemoteInstall|Virtual Remote installs]]
| [[QA/Test Days/2009-02-26|2009-02-26]] || Open Slot
|- style="background-color:#def3fe;"
| 2009-03-03 || Feature Freeze--Planning & Development Ends
|-
|-
| [[QA/Test Days/2008-09-18|2008-09-18]] || Postponed (see [https://www.redhat.com/archives/fedora-test-list/2008-September/msg00391.html fedora-test-list])
| [[QA/Test Days/2009-03-05|2009-03-05]] || Open Slot
|- style="background-color:#def3fe;"
| 2009-03-10 || Beta Freeze
|-
|-
| [[QA/Test Days/2008-09-25|2008-09-25]] || [[Anaconda/Features/FirstAidKit|FirstAidKit]] and [https://fedoraproject.org/wiki/Releases/10/Beta/ReleaseNotes F10 Beta] Live Image testing
| [[QA/Test Days/2009-03-12|2009-03-12]] || Open Slot
|-
|-
| [[QA/Test Days/2008-10-02|2008-10-02]] || [[Anaconda/Features/NetConfigForNM|Anaconda NetworkManager Config]] and [[Releases/10/Beta/ReleaseNotes|F10 Beta]]
| [[QA/Test Days/2009-03-19|2009-03-19]] || Open Slot
|- style="background-color:#def3fe;"
| 2009-03-24 || Beta Release
|-
|-
| [[QA/Test Days/2008-10-09|2008-10-09]] || [[Features/GlitchFreeAudio|Glitch Free Audio]] and [[Releases/10/Beta/ReleaseNotes|F10 Beta]]
| [[QA/Test Days/2009-03-26|2009-03-26]] || Open Slot
|-
|-
| [[QA/Test Days/2008-10-16|2008-10-16]] || [[Features/BetterLIRCSupport|Better LIRC Support]] and [[Features/SecurityAudit|Security Audit]]
| [[QA/Test Days/2009-04-02|2009-04-02]] || Open Slot
|- style="background-color:#def3fe;"
| 2009-04-07 ||Software Translation Deadline
|-
|-
| [[QA/Test Days/2008-10-23|2008-10-23]] || [https://www.redhat.com/archives/fedora-devel-announce/2008-October/msg00012.html Snapshot#2] and [https://www.redhat.com/archives/fedora-test-list/2008-October/msg01179.html Install Guide]
| [[QA/Test Days/2009-04-09|2009-04-09]] || Open Slot
|- style="background-color:#def3fe;"
| 2009-04-14 ||Final Development Freeze
|-
|-
| [[QA/Test Days/2008-10-30|2008-10-30]] || [[Releases/10/FeatureList|F10 Feature Review]]
| [[QA/Test Days/2009-04-16|2009-04-16]] || Open Slot
|-
|-
| [[QA/Test Days/2008-11-06|2008-11-06]] || [https://www.redhat.com/archives/fedora-test-list/2008-November/msg00153.html Preview Release Testing]
| [[QA/Test Days/2009-04-23|2009-04-23]] || Open Slot
|- style="background-color:#def3fe;"
| 2009-04-28 || Preview Release
|-
|-
| [[QA/Test Days/2008-11-13|2008-11-13]] || Preview Release Testing
| [[QA/Test Days/2009-04-30|2009-04-30]] || Open Slot
|-
|-
| [[QA/Test Days/2008-11-20|2008-11-20]] || Preview Release Testing
| [[QA/Test Days/2009-05-07|2009-05-07]] || Open Slot
|- style="background-color:#def3fe;"
| 2009-05-12 || Compose & Stage Release Candidate
|-
|-
| [[QA/Test Days/2008-11-25|2008-11-25]] || General Availability (GA)
| [[QA/Test Days/2009-05-14|2009-05-14]] || Open Slot
|-
|-
| [[QA/Test Days/2009-05-21|2009-05-21]] || Open Slot
|- style="background-color:#def3fe;"
| 2009-05-26 || Fedora 11 Final Release
|}
|}


Revision as of 13:11, 16 January 2009

What are Test Days?

Test Days are an opportunity to exercise a completed, or in-development, Feature planned for an upcoming Fedora release. Each Test Day brings something unique and you're encouraged to join and share your ideas, tests, and results.

When are Test Days?

Test Days occur every Thursday between the Alpha and GA milestones of a Fedora release.

The Test Day schedule for previous releases is available at:

For a list of planned test day topics, see below.

Date Topic(s)
See F11 schedule and F11 features
2009-01-20 Alpha Freeze
2009-01-22 Open Slot
2009-01-29 Open Slot
2009-02-03 Alpha Release
2009-02-05 Open Slot
2009-02-12 Open Slot
2009-02-19 Open Slot
2009-02-26 Open Slot
2009-03-03 Feature Freeze--Planning & Development Ends
2009-03-05 Open Slot
2009-03-10 Beta Freeze
2009-03-12 Open Slot
2009-03-19 Open Slot
2009-03-24 Beta Release
2009-03-26 Open Slot
2009-04-02 Open Slot
2009-04-07 Software Translation Deadline
2009-04-09 Open Slot
2009-04-14 Final Development Freeze
2009-04-16 Open Slot
2009-04-23 Open Slot
2009-04-28 Preview Release
2009-04-30 Open Slot
2009-05-07 Open Slot
2009-05-12 Compose & Stage Release Candidate
2009-05-14 Open Slot
2009-05-21 Open Slot
2009-05-26 Fedora 11 Final Release

Where are Test Days held?

Discussion is typically held on IRC in the #fedora-qa channel. There are quite a few different IRC clients out there you can use to join the discussion, including:

How To Get Involved

Bug Triage

Much like a field hospital, bug triage describes the art of quickly addressing the big issues in a bug, and moving it on for further review by the development team. Unlike a field hospital, there should be no blood or gunfire. The triage process has generated quite a following. As outlined on the BugZappers home, triage is a several step process:

  1. Getting started
  2. Finding bugs to triage
    • The list of bugs will be included in each Test Day
  3. Taking action

One should not spend more than 5 minutes triaging a single bug. If you have more time to spare, and are looking to get a bit more involved, please proceed with Bug Verification or Test Execution.

Bug Verification

FIXME

Test Execution

Often a Test Day will include focus areas for which to target when testing a Feature. These areas have been identified as critical components of the feature. If looking for a quick list of areas to target, these make great candidates.

Exploratory Testing

Exploratory testing is an approach to software testing that is not scripted or planned in as much detail as a more traditional test plan. Rather than walking through a series of pre-defined test cases, the tester is asked to think about the high-level test areas in the software. From there, the tester is encouraged to use their knowledge of the product and the code in order to navigate through different areas of the software. As they walk through the software, their emphasis is to find bugs, expose new test areas, and learn more about the product to help guide future test efforts.

The simplest definition from Exploratory Testing Explained by James Bach works the best: 

Exploratory testing is simultaneous learning, test design, and test execution.

For further reading on exploratory testing can be found at http://en.wikipedia.org/wiki/Exploratory_testing.

FAQ

What build should I test?

Each Test Day will indicate which build will be under test. Note, the nature of the build may also depend on the Feature being tested. For example, testing of a kernel feature may only require updating to the rawhide kernel package. However, testing of a custom spin of Fedora may require downloading, or building, a LiveCD.

I found a bug, what now?

FIXME

Feedback

FIXME

Retrieved from "https://fedoraproject.org/w/index.php?title=QA/Test_Days&oldid=71156"