From Fedora Project Wiki

< QA‎ | Test Days

(include exploratory testing testcase when possible)
(make it a more useful template for new test day pages, instead of a guide for interested teams. QA creates test days pages mostly anyways. A simple guide is still kept in wiki comments inside the page source.)
Line 1: Line 1:
 
{{Infobox_group
 
{{Infobox_group
| name = <<TEST DAY 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 = <<FIXME>>
+
| date = '''<<FIXME>>'''
 
| time = all day
 
| time = all day
 
| website = [[QA/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])
+
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([https://webchat.freenode.net/?channels=fedora-test-day webirc])
 
| fedora_mailing_list = test
 
| fedora_mailing_list = test
 
}}
 
}}
Line 13: Line 13:
 
== What to test? ==
 
== What to test? ==
  
Today's instalment of Fedora [[QA/Test Days|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 ==
 
== 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]] (irc_nick1), [[User:Developer2|Developer2]] (irc_nick2) '''FIXME'''
* Quality Assurance - [[User:Tester1|Tester1]] (irc_nick3), [[User:Tester2|Tester2]] (irc_nick4)
+
* 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 [[How to use IRC|IRC]]. See the infobox on top of the page to learn the right IRC channel.
  
 
== Prerequisite for Test Day ==  
 
== 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 33 (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
 
* 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:
 
 
 
* An updated [https://getfedora.org/workstation/prerelease Fedora XX pre-release], or a [https://www.happyassassin.net/nightlies.html Fedora XX nightly image]
 
  
 
== How to test? ==
 
== How to test? ==
  
 +
<!--
 
High level details on how a contributor can get involved.  This can include (but not limited to):
 
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 target with exploratory testing
* A list of pre-defined test cases to execute
+
* Areas to put special focus on
* How to report back results
+
* 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
  
Here's another common chunk (again, replace XX as above):
+
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.
 
+
-->
=== '''Update your machine''' ===
 
 
 
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:
 
 
 
=== '''Live image''' ===
 
 
 
Instead of testing with an installed system, you may download a non-destructive nightly live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]]. Live image links can be found [https://www.happyassassin.net/nightlies.html here]: please be sure to download one for the correct release.
 
 
 
=== Run the tests ===
 
  
If not using the Test Day app, provide a list of test areas or test cases that you'd like contributors to execute. For examples, see [[:Category:Test_Cases]]. If possible, always include [[QA:Testcase Exploratory Testing|Exploratory Testing]] among test cases. If using the Test Day app, link to it here, with some explanation, e.g.:
+
Visit the '''[http://testdays.fedorainfracloud.org/events/NUMBER 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.
  
Visit the [http://testdays.fedorainfracloud.org/events/NUMBER result 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 ==
 
== Reporting bugs ==
  
Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
+
<!--
 +
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.
 +
-->
  
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.
+
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 on IRC (see instructions above).
  
 
== Test Results ==
 
== Test Results ==
  
If you use the [http://testdays.fedorainfracloud.org/events Test Days app], just explain that users should enter results there and they will be transferred to the page later. For e.g.:
+
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.
 
 
Please enter your results on the [http://testdays.fedorainfracloud.org/events/NUMBER result page]. The results will be transferred here after the Test Day is finished.
 
 
 
Otherwise, 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 text to explain reporting. Here is a common setup:
 
  
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. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line.
+
<!--
 +
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
 
! User
! [[QA:Testcase_sample_1|Sample test 1]]
+
! [[QA:Testcase_example_1|Example test 1]]
! [[QA:Testcase_sample_2|Sample test 2]]
+
! [[QA:Testcase_example_2|Example test 2]]
! [[QA:Testcase_sample_3|Sample test 3]]
+
! [[QA:Testcase_example_3|Example test 3]]
! [[QA:Testcase_sample_4|Sample test 4]]
+
! [[QA:Testcase_example_4|Example test 4]]
 
! References
 
! References
 
|-
 
|-
| [[User:SampleUser|Sample User]]
+
| [[User:ExampleUser|Example User]]
 
| {{result|none}}  
 
| {{result|none}}  
 
| {{result|pass}}
 
| {{result|pass}}
Line 89: Line 77:
 
|-
 
|-
 
|}
 
|}
 +
-->
  
<!-- remove this comment block when creating a real Test Day
+
<!-- uncomment this line when creating a real Test Day
[[Category:Fedora 24 Test Days]]
+
[[Category:Fedora 33 Test Days]]
 
-->
 
-->
  
<!-- remove this category when creating a test day page -->
+
<!-- remove the line below when creating a real Test Day -->
 
[[Category:QA Templates]]
 
[[Category:QA Templates]]

Revision as of 13:13, 17 June 2020

<<FIXME TEST DAY NAME>>
Test-days-banner.svg

Date <<FIXME>>
Time all day

Website QA/Test Days
IRC #fedora-test-day (webirc)
Mailing list test


Note.png
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 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 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:

You can chat with us on IRC. See the infobox on top of the page to learn the right IRC channel.

Prerequisite for Test Day

  • A virtual machine or a bare metal machine
  • An installation of Fedora 33 (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 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 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 on IRC (see instructions above).

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.