From Fedora Project Wiki
(don't hardcode Bugzilla in the admon) |
(first choice is upstream bug tracker) |
||
| Line 2: | Line 2: | ||
{{Infobox_group | {{Infobox_group | ||
| name = ''' | | name = '''FIXME TEST DAY NAME''' | ||
| image = [[File:test-days-banner.svg|300px|link=QA/Test Days]] | | image = [[File:test-days-banner.svg|300px|link=QA/Test Days]] | ||
| date = ''' | | date = '''FIXME''' | ||
<!-- The testdays app will parse this, so please make sure to have it in format 'date = YYYY-MM-DD' or 'date = YYYY-MM-DD to YYYY-MM-DD' --> | <!-- The testdays app will parse this, so please make sure to have it in format 'date = YYYY-MM-DD' or 'date = YYYY-MM-DD to YYYY-MM-DD' --> | ||
| time = all day | | time = all day | ||
| Line 19: | Line 19: | ||
<!-- Describe in detail what this test day is about and why would users want to participate in it. What makes this interesting for them? What's new and exciting in your software or a feature? --> | <!-- Describe in detail what this test day is about and why would users want to participate in it. What makes this interesting for them? What's new and exciting in your software or a feature? --> | ||
This [[QA/Test Days|Test Day]] will focus on ''' | This [[QA/Test Days|Test Day]] will focus on '''FIXME''' | ||
== Who's available == | == Who's available == | ||
| Line 47: | Line 47: | ||
--> | --> | ||
Visit the '''[http://testdays. | Visit the '''[http://testdays.fedoraproject.org/events/NUMBER FIXME results page]''' and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the ''Enter result'' button for the test. | ||
Please also try to experiment and explore and perform tasks not mentioned in any of the pre-defined test cases. | Please also try to [[QA:Testcase_Exploratory_Testing|experiment and explore]] and perform tasks not mentioned in any of the pre-defined test cases. | ||
== Reporting bugs == | == Reporting bugs == | ||
| Line 57: | Line 57: | ||
--> | --> | ||
All bugs should be reported into '''[https://bugzilla.redhat.com Bugzilla]''', in most cases against the <code>FIXME</code> component. If you are unsure about exactly how to file the report or what other information to include, just ask us | All bugs should be reported into the '''[https://FIXME FIXME upstream bug tracker]'''. A less-preferred alternative is to file them into '''[https://bugzilla.redhat.com Red Hat Bugzilla]''', in most cases against the <code>FIXME</code> component. If you are unsure about exactly how to file the report or what other information to include, just [[#Who's_available|ask us]]. | ||
== Test Results == | == Test Results == | ||
| Line 84: | Line 84: | ||
<!-- uncomment this line when creating a real Test Day | <!-- uncomment this line when creating a real Test Day | ||
[[Category:Fedora | [[Category:Fedora 38 Test Days]] | ||
--> | --> | ||
<!-- remove the line below when creating a real Test Day --> | <!-- remove the line below when creating a real Test Day --> | ||
[[Category:QA Templates]] | [[Category:QA Templates]] | ||
Revision as of 15:37, 1 March 2023
| FIXME TEST DAY NAME | |
|---|---|
| |
| Date | FIXME |
| Time | all day |
| Website | QA/Test Days |
| Matrix | #test-day:fedoraproject.org |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.
What to test?
This Test Day will focus on FIXME
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion:
- Development - Developer1 (irc_nick1), Developer2 (irc_nick2) FIXME
- Quality Assurance - Sumantro Mukherjee (sumantrom), Geoffrey Marr (coremodule), Kamil Paral (kparal), Adam Williamson (adamw)
You can chat with us on Matrix or IRC. See the infobox on top of the page to learn where to join.
Prerequisite for Test Day
- A virtual machine or a bare metal machine
- An installation of Fedora 38 (any Edition or Spin). Make sure to fully update your system. If installing a fresh system, it's recommended to use the latest nightly image.
How to test?
Visit the FIXME results page and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the Enter result button for the test.
Please also try to experiment and explore and perform tasks not mentioned in any of the pre-defined test cases.
Reporting bugs
All bugs should be reported into the FIXME upstream bug tracker. A less-preferred alternative is to file them into Red Hat Bugzilla, in most cases against the FIXME component. If you are unsure about exactly how to file the report or what other information to include, just ask us.
Test Results
Test results will be exported here once the test day is over. See How to test? section for information how to submit results and see the live results.