QA/Test Days/Template: Difference between revisions

Latest revision as of 12:55, 18 January 2024

FIXME TEST DAY NAME


Date	FIXME
Time	all day

Website	QA/Test Days
Matrix	#test-day:fedoraproject.org^{(other clients\|?)}
Mailing list	test

Can't make the date?
If you come to this page 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 (matrix_nick1), Developer2 (matrix_nick2) FIXME
Quality Assurance - Sumantro Mukherjee (sumantrom), Geoffrey Marr (coremodule), Kamil Paral (kparal), Adam Williamson (adamw)

You can chat with us on Matrix. 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 40 (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

Perhaps you've found an already-reported bug. Please look at:

All new 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.

We really need bug reports!
Please note that just mentioning your problem into the comments section on the results page is not very helpful. Very often those problems only happen in specific circumstances, or with specific steps taken. We need the logs and screenshots, and we need to be able to ask you followup questions. Please file bug reports, it's much more useful than a short comment. Thank you!

When filing the bug, it's very helpful to include:

exact steps you've performed (and whether you can reproduce it again)
screenshots or videos, if applicable
system journal (log), which you can retrieve by journalctl -b > journal.txt
all output in a terminal, if started from a terminal
your system description

If you are unsure about exactly how to file the report or what other information to include, just ask us.

Please make sure to link to the bug when submitting your test result, thanks!

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.

@@ Line 1: / Line 1: @@
+<!-- Make sure the pages is named as "Test Day:YYYY-MM-DD topic" -->
 {{Infobox_group
-| name = Fedora Test Days
+| name = '''FIXME TEST DAY NAME'''
-| image = [[File:Echo-testing-48px.png|link=QA/Fedora_15_test_days]]
+| image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]
-| caption = [[FIXME|FIXME]]
+| date = '''FIXME'''
-| 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' -->
 | time = all day
-| website = [[QA/Fedora_15_test_days]]
+| website = [[QA/Test Days]]
-| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
+| matrix = {{matrix|#test-day:fedoraproject.org}}
 | fedora_mailing_list = test
 }}
-{{admon/note | 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 at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}
+{{admon/note | Can't make the date? | If you come to this page 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 [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}}
 == What to test? ==
-Today's installment of Fedora Test Day will focus on '''<<FIXME>>'''
+<!-- 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 '''FIXME'''
 == Who's available ==
-The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
+The following cast of characters will be available testing, workarounds, bug fixes, and general discussion:
-* Development - [[User:Developer1|Developer1]] (irc_nick1), [[User:Developer2|Developer2]] (irc_nick2)
+* Development - [[User:Developer1|Developer1]] (matrix_nick1), [[User:Developer2|Developer2]] (matrix_nick2) '''FIXME'''
-* Quality Assurance - [[User:Tester1|Tester1]] (irc_nick3), [[User:Tester2|Tester2]] (irc_nick4), [[User:Tester3|Tester3]] (irc_nick5)
+* Quality Assurance - [[User:Sumantrom|Sumantro Mukherjee]] (sumantrom), [[User:coremodule|Geoffrey Marr]] (coremodule), [[User:kparal|Kamil Paral]] (kparal), [[User:adamw|Adam Williamson]] (adamw)
+You can chat with us on [https://docs.fedoraproject.org/en-US/project/communications/ Matrix]. See the infobox on top of the page to learn where to join.
 == Prerequisite for Test Day ==
-List any prerequisite needs for the test event.  A fresh system, virtualized guest, a blank DVD ... a desire to break software?
+* A virtual machine or a bare metal machine
+* An installation of Fedora 40 (any Edition or Spin). Make sure to fully update your system. If installing a fresh system, it's recommended to use the latest [https://www.happyassassin.net/nightlies.html nightly image].
-* Usb key
+== How to test? ==
-* Usb externally connected HD IDE/SATA
-* Empty HD IDE/SATA/SCSI
-* Free space on HD
-Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:
+<!--
+High level details on how a contributor can get involved.  This can include (but not limited to):
+* Areas to target with exploratory testing
+* Areas to put special focus on
+* Links to documentation, if relevant
+* How to report the results
+Example: https://fedoraproject.org/wiki/Test_Day:2020-02-20_Gnome_3.36_Test_Day#How_to_test.3F
-* An updated [http://fedoraproject.org/get-prerelease Fedora XX pre-release], [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below), or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ nightly live image]
+If not using the TestDays app, provide a list of test areas or test cases that you'd like contributors to execute. For examples, see https://fedoraproject.org/wiki/Category:Test_Cases . If possible, always include https://fedoraproject.org/wiki/QA:Testcase_Exploratory_Testing among test cases. If using the TestDays app, link the test cases in it.
-* Your hardware profile uploaded to [http://www.smolts.org Smolt] according to [http://smolts.org/smolt-wiki/Main_Page#Usage these instructions]
+-->
-== How to test? ==
+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.
-High level details on how a contributor can get involved.  This can include (but not limited to):
+Please also try to [[QA:Testcase_Exploratory_Testing|experiment and explore]] and perform tasks not mentioned in any of the pre-defined test cases.
-* Areas to target with exploratory testing
+== Reporting bugs ==
-* A list of pre-defined test cases to execute
-* How to report back results
-Here's another common chunk (again, replace XX as above):
+<!--
+If there are multiple places where to report bugs (e.g. general GNOME bugs go into upstream GNOME GitLab, and only packaging issues or non-GNOME bugs go to Red Hat Bugzilla), mention it and advise users where to file which issues.
+-->
-=== '''Update your machine''' ===
+Perhaps you've found an already-reported bug. Please look at:
+* [https://qa.fedoraproject.org/blockerbugs/milestone/40/beta/buglist Fedora 40 Beta blocker bugs]
+* [https://qa.fedoraproject.org/blockerbugs/milestone/40/final/buglist Fedora 40 Final blocker bugs]
-If you're running Fedora XX, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide. Or:
+All new 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.
-=== '''Live image''' ===
+{{admon/tip | We really need bug reports! | Please note that just mentioning your problem into the comments section on the results page is not very helpful. Very often those problems only happen in specific circumstances, or with specific steps taken. We need the logs and screenshots, and we need to be able to ask you followup questions. Please file bug reports, it's much more useful than a short comment. Thank you!}}
-Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]]. Live images can be found [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ here].
+When filing the bug, it's very helpful to include:
+* exact steps you've performed (and whether you can reproduce it again)
+* screenshots or videos, if applicable
+* system journal (log), which you can retrieve by <code>journalctl -b > journal.txt</code>
+* all output in a terminal, if started from a terminal
+* your system description
-== Test Cases ==
+If you are unsure about exactly how to file the report or what other information to include, just [[#Who's_available|ask us]].
-Provide a list of test areas or test cases that you'd like contributors to execute.  For other examples, see [[:Category:Test_Cases]].
+Please make sure to link to the bug when submitting your test result, thanks!
 == Test Results ==
-Construct a table or list to allow testers to post results.  Each column should be a test case or configuration, and each row should consist of test results. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
+Test results will be exported here once the test day is over. See [[#How_to_test?|How to test?]] section for information how to submit results and see the live results.
-If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=udisks udisks], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=gnome-disk-utility gnome-disk-utility] for bugs in the Palimpsest graphical front end itself. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to the Smolt profile of the system you tested. For each test case, if your system worked correctly, simply enter the word '''PASS'''. If you had trouble, enter the word '''FAIL''', with a footnote indicator, and put a link to the bug report in the References column (as in the example line). For tests you could not perform, enter a dash.
+<!--
+If you're not using TestDays app for submitting test results, and want to let users input results directly into wiki, here's an example results table:
 {|
 ! User
-! Smolt Profile
+! [[QA:Testcase_example_1|Example test 1]]
-! [[QA:Testcase_sample_1|Sample test 1]]
+! [[QA:Testcase_example_2|Example test 2]]
-! [[QA:Testcase_sample_2|Sample test 2]]
+! [[QA:Testcase_example_3|Example test 3]]
-! [[QA:Testcase_sample_3|Sample test 3]]
+! [[QA:Testcase_example_4|Example test 4]]
-! [[QA:Testcase_sample_4|Sample test 4]]
 ! References
 |-
-| [[User:SampleUser|Sample User]]
+| [[User:ExampleUser|Example User]]
-| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW]
 | {{result|none}}
 | {{result|pass}}
@@ Line 82: / Line 97: @@
 |-
 |}
+-->
+<!-- uncomment this line when creating a real Test Day
+[[Category:Fedora 40 Test Days]]
+-->
-[[Category:Test Days]]
+<!-- remove the line below when creating a real Test Day -->
 [[Category:QA Templates]]

Search