|
|
| (39 intermediate revisions by 6 users not shown) |
| Line 1: |
Line 1: |
| | __NOTOC__ |
| | {{header|qa}} |
| | |
| == What are Test Days? == | | == What are Test Days? == |
|
| |
|
| Line 5: |
Line 8: |
| == When are Test Days? == | | == When are Test Days? == |
|
| |
|
| Test Days occur every Thursday between the Alpha and GA milestones of a Fedora release. | | Test Days occur on days chosen by their organizers between the Alpha and GA milestones of a Fedora 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. Detailed schedules can be found at: |
| | * [[QA/{{FedoraVersion|long|next}} test days|{{FedoraVersion|long|next}} Test Day Schedule]] |
| | * [[:Category:Test_Days|Previous test day schedules]] |
|
| |
|
| For a list of previous and planned test day topics, see the table below:
| | {{admon/note | Current test day | Use [[Test_Day:Current | this link]] to visit the current Test Day page.}} |
| | |
| {| | |
| ! 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 [[Features/ApplicationInstaller|Application Installer]]
| |
| |-
| |
| | [[QA/Test Days/2008-10-16|2008-10-16]] || [[Features/SecurityAudit|Security Audit]] and [[Features/GlitchFreeAudio|Glitch Free Audio]]
| |
| |-
| |
| | [[QA/Test Days/2008-10-23|2008-10-23]] || [[Features/Eclipse34|Eclipse 3.4]] and [[Releases/10/FeatureList|F10 Feature Review]]
| |
| |-
| |
| | [[QA/Test Days/2008-10-30|2008-10-30]] || Unspecified
| |
| |}
| |
|
| |
|
| == Where are Test Days held? == | | == Where are Test Days held? == |
|
| |
|
| 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: | | Discussion is typically held on IRC in the [irc://irc.freenode.net/fedora-test-day #fedora-test-day] channel on the Freenode network. See [[How to use IRC]] for additional technical information. |
| | |
| * [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 ===
| |
| | |
| 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:
| |
| | |
| ''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 == | | == FAQ == |
|
| |
|
| === What build should I test? ===
| | * [[QA/SOP_Test_Day_management|SOP Guide for hosting a test day]] |
| | | * [[QA/Test Days/Create|How do I propose a test day?]] |
| 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.
| | * [[QA/Test Days/Live Image|How do I build a test day live image?]] |
| | |
| === I found a bug, what now? ===
| |
| | |
| FIXME
| |
| | |
| == Feedback ==
| |
|
| |
|
| FIXME
| | [[Category:Test Days]] |
