From Fedora Project Wiki

< QA

m (Added links)
(use {{matrix}} template)
 
(59 intermediate revisions by 10 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.
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.


For a list of previous and planned test day topics, see the table below:
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 Matrix 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.
! Date !! Topic(s)
|+align="bottom"|See [[Releases/10/Schedule|F10 schedule]] and [[Releases/10/FeatureList|F10 features]]
|-
| [[QA/Test Days/2008-08-14|2008-08-14]] || [[Anaconda/Features/EncryptedBlockDevices|EncryptedBlock Devices]] and [[Features/BetterStartup|Plymouth]]
|-
| [[QA/Test Days/2008-08-21|2008-08-21]] || Postponed (see [https://www.redhat.com/archives/fedora-test-list/2008-August/msg00318.html fedora-test-list])
|-
| [[QA/Test Days/2008-08-28|2008-08-28]] || [[Features/BetterPrinting|BetterPrinting]] and [[Features/ApplianceTools|ApplianceTools]]
|-
| [[QA/Test Days/2008-09-04|2008-09-04]] || [[Anaconda/Features/SaveToBugzilla|Save to Bugzilla]] and [[Features/ConnectionSharing|Connection Sharing]]
|-
| [[QA/Test Days/2008-09-11|2008-09-11]] || [[Features/VirtStorage|Virtual Storage]] and [[Features/VirtRemoteInstall|Virtual Remote installs]]
|-
| [[QA/Test Days/2008-09-18|2008-09-18]] || Postponed (see [https://www.redhat.com/archives/fedora-test-list/2008-September/msg00391.html fedora-test-list])
|-
| [[QA/Test Days/2008-09-25|2008-09-25]] || [[Anaconda/Features/FirstAidKit|FirstAidKit]] and [https://fedoraproject.org/wiki/Releases/10/Beta/ReleaseNotes F10 Beta] Live Image testing
|-
| [[QA/Test Days/2008-10-02|2008-10-02]] || [[Anaconda/Features/NetConfigForNM|Anaconda NetworkManager Config]] and [[Releases/10/Beta/ReleaseNotes|F10 Beta]]
|-
| [[QA/Test Days/2008-10-09|2008-10-09]] || [[Features/GlitchFreeAudio|Glitch Free Audio]] and [[Releases/10/Beta/ReleaseNotes|F10 Beta]]
|-
| [[QA/Test Days/2008-10-16|2008-10-16]] || [[Features/BetterLIRCSupport|Better LIRC Support]] and [[Features/SecurityAudit|Security Audit]]
|-
| [[QA/Test Days/2008-10-23|2008-10-23]] || [https://www.redhat.com/archives/fedora-devel-announce/2008-October/msg00012.html Snapshot#2] and [https://www.redhat.com/archives/fedora-test-list/2008-October/msg01179.html Install Guide]
|-
| [[QA/Test Days/2008-10-30|2008-10-30]] || [[Releases/10/FeatureList|F10 Feature Review]]
|-
| [[QA/Test Days/2008-11-06|2008-11-06]] || [https://www.redhat.com/archives/fedora-test-list/2008-November/msg00153.html Preview Release Testing]
|-
| [[QA/Test Days/2008-11-13|2008-11-13]] || Preview Release Testing
|-
| [[QA/Test Days/2008-11-20|2008-11-20]] || Preview Release Testing
|-
| [[QA/Test Days/2008-11-25|2008-11-25]] || General Availability (GA)
|-
|}


== Where are Test Days held? ==
{{anchor|when}}
 
== When are Test Days? ==
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:
 
* [http://embed.mibbit.com/?server=irc.freenode.net&channel=%23fedora-qa&forcePrompt=true Web-based mibbit] (no additional software required)
* [https://addons.mozilla.org/firefox/16/ Chatzilla firefox extension]
* A list of [http://www.ircreviews.org/clients/platforms-unix.html popular linux clients]
 
== 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:
 
# [[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 ===
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).


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. 
'''[https://calendar.fedoraproject.org/list/QA/?subject=Test+Day See current Test Day schedule]'''


The simplest definition from [http://www.satisfice.com/articles/et-article.pdf Exploratory Testing Explained by James Bach] works the best:
'''[[Test Day:Current|See the most recent Test Day page]]'''


''Exploratory testing is simultaneous learning, test design, and test execution.''
{{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.}}


For further reading on exploratory testing can be found at http://en.wikipedia.org/wiki/Exploratory_testing.
== How to participate in a Test Day? ==


== FAQ ==
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).


=== What build should I test? ===
Discussion is typically held on Matrix in the {{matrix|#test-day:fedoraproject.org}} room. See [https://docs.fedoraproject.org/en-US/project/communications/ Communication in Fedora] for additional information on Matrix. Some Test Days might use a different chat room, but it is always specified on the Test Day page.


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.
== How to propose a Test Day? ==


=== I found a bug, what now? ===
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?]]


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


== Feedback ==
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]]


FIXME
[[Category:Test Days]]

Latest revision as of 12:43, 18 January 2024

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 Matrix 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 Matrix in the #test-day:fedoraproject.org(other clients|?) room. See Communication in Fedora for additional information on Matrix. Some Test Days might use a different chat room, 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: