User:Johannbg/Draft/QA/Test Days

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.

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:

• Web-based mibbit (no additional software required)
• Chatzilla firefox extension
• A list of popular linux clients

How To Get Involved

Suggestion Box

Have an idea for an upcoming test day topic? Please drop me a line if you'd like to request a Test Day topic.

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.

Feedback

Don't hesitate to send your thoughts, comments or suggestions.

DATE	TIME	WHERE
$Date	From $Time to $Time UTC	#fedora-qa (need irc help?)

How to join?

For information on joining a Fedora Test Day, see QA/Test_Days#Where_are_Test_Days_held.3F

What to test?

This week's instalment of Fedora Test Day will focus on:

• Features/20SecondStartup

Preparing for Test Day

Depending on the speed of your connection and the time available for testing, there are several methods available for

Live Images

1. Please download a live ISO image for your architecture:
   • i686
   • x86_64
2. Prepare your live image by following the instructions at FedoraLiveCD
3. Or run the dowloaded ISO image in qemu:

    su -c 'qemu -cdrom Fedora-11-Alpha-i686-Live.iso -m 512 -std-vga'

Install Media

1. Consult the installation guide for quick start information to determine the best install method for your needs.
2. Follow instructions for installing your system.
   • Alternatively, on an already installed system:
     1. Install snake:

        yum install snake

     2. Configure your system for installation:

        snake-install http://download.fedora.redhat.com/pub/fedora/linux/releases/test/11-Alpha/Fedora/i386/os

Need help?

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 ...

• Development - User:Sandeen
• Quality Assurance - User:Johannbg, User:jlaska, User:wwoods

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