From Fedora Project Wiki

Thu September 4, 2008 From 12:00 to 21:00 UTC (8am -> 5pm EDT) #fedora-qa (need irc help?)

This week's instalment of Fedora Test Day will focus on 2 additional features planned for the Fedora 10 release. On the agenda will be:

We'll have a host of QA and Development characters hanging out discussing bugs (aka "features"), expectations, and test areas. I've included details below for how you can contribute below.

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

Want to join in?
If you'd like to sign up to help field questions, please add your name to the list above.

Triage NEW Bugs[edit]

Much like a field hospital, bug triage is 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 guts. The triage process has generated quite a following. You are encouraged to read more about the triage process on the BugZappers home. In a nutshell, bug triage is a several step process that includes:

  1. Getting started
  2. Finding bugs to triage, the list we'll use for Test Day includes:
    • NEW anaconda bugs
    • NEW NetworkManager bugs
  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.

Review Proposed Test Plan[edit]

See a typo or spot a gap in coverage in the proposed test plans for these features? Either modify the pages noted below, or come to #fedora-qa to discuss your suggestions. Help improve this feature by making changes/suggestions.


Getting Started[edit]

To help with testing, you'll need to get a copy of the Fedora 10 Alpha. Additionally, since the Test Day involves testing installation, you'll likely need a spare system to install to.

Here are some testing requirements:

  • A spare system (can be a virtual guest)
  • Access to install F10-Alpha install media (mirror list)
  • Optical CD/DVD media and a media burner (optional)

One you have selected a mirror, you must decide how you'd like to start the installer. There are many options, but the following lists the most popular choices.

Installation from CD/DVD[edit]

This method requires:

  • A spare system (can be a virtual guest)
  • Optical CD/DVD media and a media burner (optional)

The same process used to install an Fedora release can be used to install F10-Alpha. For an overview of the process, please review the Installation Guide.

  1. First, determine your system architecture (docs).
  2. Next, locate a nearby mirror where you can download install media (mirror list).
  3. Next, download a F10-Alpha Fedora CD, DVD, or boot.iso for your architecture from a (docs)
  4. Burn the downloaded image to a CD/DVD
  5. Boot from the CD/DVD
Installation from LiveUSB[edit]
Installation over Network[edit]

This method requires:

  • A spare system (can be a virtual guest) - already installed OS (F9, F10-Alpha)

Information on installing without The same process for locating installation media will be used.

  1. First, determine your system architecture (see
  2. Next, locate a nearby mirror where you can download install media (see
  3. Next, install the snake utility:
    # yum install snake
  4. Using the mirror you selected above, update your bootloader information using snake:
    # snake-install
  5. Reboot your system to start the install

With your system installed, you are ready to move on to testing. Good luck!

Updating NetworkManager Packages[edit]

Once your system is installed, you'll need to install the latest NetworkManager packages built for testing. Instructions for installing the latest packages are listed below.

1 Create a yum repo for Fedora Test Day packages ...

$ cat <<EOF>/etc/yum.repos.d/fedora-test-day.repo

2 Upgrade to the Test Day packages ...

$ yum --enablerepo=fedora-test-day --enablerepo=updates* update NetworkManager*

3 Restart the NetworkManager service

$ /sbin/service NetworkManager restart
Forcing Anaconda to Fail[edit]

While errors (referred to as tracebacks) during installation are not uncommon during the development cycle. If you need to force the installation program to fail in order to test the SaveToBugzilla functionality, the easiest way is to boot with the following command-line option:


This will cause the installation program to fail after clicking "Next" for the first time. This will present an error dialog which you can use to test SaveToBugzilla

Exploratory Testing[edit]

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

Test Areas[edit]

For our test day, let's define the following test areas as primary focus areas for exploratory testing:

  • NetworkManager
    • Fedora system sharing connections to other operating systems (Windows, OSX, Fedora, ...)
    • Exercise different wireless security settings
    • VPN over a shared connection?
  • Anaconda SaveToBugzilla
    • Invalid data (username, password, empty description, really long description)
    • Valid data, repeat several times

Targeted Testing[edit]

Not in the mood for exploratory testing? That's fine. We've taken the time to define explicit test cases for the different test areas noted above.

With a spare system(s) in hand, you are welcome to walk through one or more of the following test cases.

The goal is to flesh out any bugs in the software that might be exposed by your special hardware environment.

Test review[edit]

See a typo in the proposed test matrix? Have an interesting hardware scenario to share? Is something not clear? Help us improve the test coverage.

Come join us on #fedora-qa, ask questions, propose changes, and share your issues.

Bug Filing Tips[edit]

When filing NetworkManager bugs, please include the following information in the bug report.

  1. iwconfig output for the card
  2. /usr/bin/nm-tool output (mask AP addresses and your MAC if you like),
  3. iwlist scan output (mask AP addresses again if you like)

For assistance filing installation (anaconda) bug reports, refer to How to debug installation problems.

Known Issues[edit]

Both features have been available for testing already through rawhide. As a result, there is a list of bugs already filed for each area. Before you file a new bug, please refer to the following before filing a new bug:

    • Bug is filed, but no traceback attached, and no 0x0HASH in the whiteboard (see rhbug:461148)
    • No user feedback provided after submitting bug
    • The mouse cursor turns into an hourglass, and never turns back to a pointer