* A list of [http://www.ircreviews.org/clients/platforms-unix.html popular linux clients]

* A list of [http://www.ircreviews.org/clients/platforms-unix.html popular linux clients]

−

== How To Get Involved ==

+

== How To Schedule a Test Day? ==

−

=== Suggestion Box ===

+

* [[QA/Test Days/Propose|How do I propose a test day topic?]]

−

+

* [[QA/Test Days/Create|How do I host my own test day?]]

−

Have an idea for an upcoming test day topic? Please [mailto:jlaska\AT\fedoraproject.DOT.org drop me a line] if you'd like to request a Test Day topic.

+

−

+

−

=== 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:

+

−

+

−

# [[BugZappers/GettingStarted| Getting started]]

+

−

# [[BugZappers/FindingBugs| Finding bugs to triage]]

+

−

#* The list of bugs will be included in each Test Day

+

−

# [[BugZappers/TakingAction| 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 [http://www.satisfice.com/articles/et-article.pdf Exploratory Testing Explained by James Bach] works the best:

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.

Revision as of 15:43, 6 February 2009

Contents

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. Detailed schedules can be found at:

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, and JBoss are trademarks or registered trademarks of
Red Hat, Inc. or its subsidiaries in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
The Fedora Project is maintained and driven by the community and sponsored by Red Hat. This is a community
maintained site. Red Hat is not responsible for content.