From Fedora Project Wiki

< QA

m (Postponing eclipse-3.4 testing)
m (Added links)
Line 37: Line 37:
| [[QA/Test Days/2008-10-30|2008-10-30]] || [[Releases/10/FeatureList|F10 Feature Review]]
| [[QA/Test Days/2008-10-30|2008-10-30]] || [[Releases/10/FeatureList|F10 Feature Review]]
| [[QA/Test Days/2008-11-06|2008-11-06]] || Preview Release Testing
| [[QA/Test Days/2008-11-06|2008-11-06]] || [ Preview Release Testing]
| [[QA/Test Days/2008-11-13|2008-11-13]] || Preview Release Testing
| [[QA/Test Days/2008-11-13|2008-11-13]] || Preview Release Testing

Revision as of 14:47, 6 November 2008

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.

For a list of previous and planned test day topics, see the table below:

Date Topic(s)
See F10 schedule and F10 features
2008-08-14 EncryptedBlock Devices and Plymouth
2008-08-21 Postponed (see fedora-test-list)
2008-08-28 BetterPrinting and ApplianceTools
2008-09-04 Save to Bugzilla and Connection Sharing
2008-09-11 Virtual Storage and Virtual Remote installs
2008-09-18 Postponed (see fedora-test-list)
2008-09-25 FirstAidKit and F10 Beta Live Image testing
2008-10-02 Anaconda NetworkManager Config and F10 Beta
2008-10-09 Glitch Free Audio and F10 Beta
2008-10-16 Better LIRC Support and Security Audit
2008-10-23 Snapshot#2 and Install Guide
2008-10-30 F10 Feature Review
2008-11-06 Preview Release Testing
2008-11-13 Preview Release Testing
2008-11-20 Preview Release Testing
2008-11-25 General Availability (GA)

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


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


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?