From Fedora Project Wiki

< QA‎ | Test Days

(replace trac link)
(fix pagure link)
Line 6: Line 6:
Community members are encouraged to propose, or host, Test Days designed to focus testing around existing or upcoming Fedora features.  To propose a Test Day topic, follow the steps below.
Community members are encouraged to propose, or host, Test Days designed to focus testing around existing or upcoming Fedora features.  To propose a Test Day topic, follow the steps below.


# [https://pagure.io/fedora-qa/issues?status=all&tags=testday Create a fedora-qa ticket].
# [https://pagure.io/fedora-qa/issues?status=all&tags=test+days Create a fedora-qa ticket].
# Please include the following information:
# Please include the following information:
## ''Ownership'' - Indicate whether you plan to host and organize the test day, or if you need the QA team to be responsible for hosting and organizing the test day.  For guidance on hosting a successful test day, see [[QA/SOP_Test_Day_management]]
## ''Ownership'' - Indicate whether you plan to host and organize the test day, or if you need the QA team to be responsible for hosting and organizing the test day.  For guidance on hosting a successful test day, see [[QA/SOP_Test_Day_management]]

Revision as of 11:43, 30 July 2018

QA.png

Propose a Test Day

Community members are encouraged to propose, or host, Test Days designed to focus testing around existing or upcoming Fedora features. To propose a Test Day topic, follow the steps below.

  1. Create a fedora-qa ticket.
  2. Please include the following information:
    1. Ownership - Indicate whether you plan to host and organize the test day, or if you need the QA team to be responsible for hosting and organizing the test day. For guidance on hosting a successful test day, see QA/SOP_Test_Day_management
    2. Time frame - Examine the current test day schedule and the current release schedule and provide us with your preferred test day dates. We usually use Thursdays for test days, or Tuesdays if Thursdays are already occupied.
    3. Feature(s) - If applicable, provide a link to the applicable feature(s) (see Releases/40/FeatureList).
Note.png
Living document...
These pages do not have to be complete and are useful for brainstorming or work in progress.