From Fedora Project Wiki

< QA

m (Added category)
(reword the whole page. Add useful information, make the import links stand out more)
(45 intermediate revisions by 9 users not shown)
Line 1: Line 1:
== What are Test Days? ==
__NOTOC__
{{autolang|base=yes}}


Test Days are an opportunity to exercise a completed, or in-development, [[Features|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.
[[Image:test-days-banner.svg|right|400px]]


== When are Test Days? ==
== What are Test Days? ==


Test Days occur every ''Thursday'' between the Alpha and GA milestones of a Fedora release.  Detailed schedules can be found at:
Test Days are often focused on testing [[Changes]] planned for an upcoming Fedora release, but they also regularly test important areas of the Fedora distribution, like upgrades, internationalization, graphical drivers, desktop environments, kernel updates, and others.
* [[QA/Test Days/F11|Fedora 11 Test Day Schedule]]
* [[QA/Test Days/F10|Fedora 10 Test Day Schedule]]


== Where are Test Days held? ==
We welcome anyone who is willing to join, test the software or features in question, and report success or issues. Each Test Day has an IRC channel dedicated for support, and developers are available to chat and help debug issues. This is a great opportunity to meet people who create said software and discuss any issues you might have with it in a live conversation.


Discussion is typically held on IRC in the [irc://irc.freenode.net/fedora-qa #fedora-qa] channel.  There are quite a few different IRC clients out there you can use to join the discussion, including:
By attending Test Days you help us verify that the upcoming Fedora release has sufficient quality, or identify important issues and make sure they are resolved before full release.


* [http://embed.mibbit.com/?server=irc.freenode.net&channel=%23fedora-qa&forcePrompt=true Web-based mibbit] (no additional software required)
{{anchor|when}}
* [https://addons.mozilla.org/firefox/16/ Chatzilla firefox extension]
== When are Test Days? ==
* A list of [http://www.ircreviews.org/clients/platforms-unix.html popular linux clients]
 
== How To Get Involved ==
 
=== Suggestion Box ===
 
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. 
Test Days occur on days chosen by their organizers between the [[Releases/Branched|branch date]] and its [[Fedora Release Life Cycle|full release]], but testing performed before or after the official Test Day is also useful and we encourage people to add their results and file bugs even if they cannot make the date. (Note that if you test ''ahead'' of the planned date, the instructions might not be finalized yet and the software itself might not be completely ready).


The simplest definition from [http://www.satisfice.com/articles/et-article.pdf Exploratory Testing Explained by James Bach] works the best:
'''[https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day See current Test Day schedule]'''


''Exploratory testing is simultaneous learning, test design, and test execution.''
'''[[Test Day:Current|See the most recent Test Day page]]'''


For further reading on exploratory testing can be found at http://en.wikipedia.org/wiki/Exploratory_testing.
{{admon/note | Get notified about upcoming Test Days | You can [[QA#calendar|add the QA calendar]] into your calendar software (Google Calendar, Thunderbird, etc) to always see an up-to-date information about upcoming Test Day events. Alternatively, you can [[QA#Communicate|subscribe to the test-announce list]] to receive email notifications.}}


== FAQ ==
== How to participate in a Test Day? ==


=== What build should I test? ===
Simply follow the instructions on the Test Day page. Most Test Days require an installed system. It's better to use a real hardware, but often it's possible to just use a virtual machine. The page will have links to installation images and instructions how to set the system up. Note that Fedora development releases are not stable and you should think twice before installing them alongside your production system (or at least make sure to have backups).


Each Test Day will indicate which build will be under test.  Note, the nature of the build may also depend on the Feature being testedFor 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.
Discussion is typically held on IRC in the [https://webchat.freenode.net/?channels=#fedora-test-day #fedora-test-day] channel on the Freenode networkSee [[How to use IRC]] for additional technical information. Some Test Days might use a different channel, but it is always specified on the Test Day page.


=== I found a bug, what now? ===
== How to propose a Test Day? ==


FIXME
If you are a member of a team who could benefit from running a Test Day, we want to hear from you! We'll help you set it up and promote it in the community. Please read:
* [[QA/Test Days/Create|How do I propose a test day?]]


== Feedback ==
== How to organize a Test Day? ==


Don't hesitate to send your [mailto:jlaska\AT\fedoraproject.DOT.org thoughts, comments or suggestions].
If you are a QA member or simply interested in getting involved in the Test Day creation process, here is some related documentation and links:
* [https://pagure.io/fedora-qa/issues?status=all&tags=test+days Test Days tickets]
* [[QA/SOP_Test_Day_management|SOP guide for hosting a test day]]
* [[QA/Test Days/Live Image|How to build a test day live image]]
* [[:Category:Test_Days|Previous test day schedules]]


[[Category:Test Days]]
[[Category:Test Days]]

Revision as of 08:33, 9 April 2020

Test-days-banner.svg

What are Test Days?

Test Days are often focused on testing Changes planned for an upcoming Fedora release, but they also regularly test important areas of the Fedora distribution, like upgrades, internationalization, graphical drivers, desktop environments, kernel updates, and others.

We welcome anyone who is willing to join, test the software or features in question, and report success or issues. Each Test Day has an IRC channel dedicated for support, and developers are available to chat and help debug issues. This is a great opportunity to meet people who create said software and discuss any issues you might have with it in a live conversation.

By attending Test Days you help us verify that the upcoming Fedora release has sufficient quality, or identify important issues and make sure they are resolved before full release.

When are Test Days?

Test Days occur on days chosen by their organizers between the branch date and its full release, but testing performed before or after the official Test Day is also useful and we encourage people to add their results and file bugs even if they cannot make the date. (Note that if you test ahead of the planned date, the instructions might not be finalized yet and the software itself might not be completely ready).

See current Test Day schedule

See the most recent Test Day page

Note.png
Get notified about upcoming Test Days
You can add the QA calendar into your calendar software (Google Calendar, Thunderbird, etc) to always see an up-to-date information about upcoming Test Day events. Alternatively, you can subscribe to the test-announce list to receive email notifications.

How to participate in a Test Day?

Simply follow the instructions on the Test Day page. Most Test Days require an installed system. It's better to use a real hardware, but often it's possible to just use a virtual machine. The page will have links to installation images and instructions how to set the system up. Note that Fedora development releases are not stable and you should think twice before installing them alongside your production system (or at least make sure to have backups).

Discussion is typically held on IRC in the #fedora-test-day channel on the Freenode network. See How to use IRC for additional technical information. Some Test Days might use a different channel, but it is always specified on the Test Day page.

How to propose a Test Day?

If you are a member of a team who could benefit from running a Test Day, we want to hear from you! We'll help you set it up and promote it in the community. Please read:

How to organize a Test Day?

If you are a QA member or simply interested in getting involved in the Test Day creation process, here is some related documentation and links: