(instead of using QA/Fedora_NN_test_days, let's just use QA/Test_Days. don't hardcode Adam as the test day runner everywhere :-). include a specific category and include a comment to remove a template category) |
(wow, this was getting pretty hoary. update for current best practice, better links, etc etc) |
||
| Line 33: | Line 33: | ||
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending: | Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending: | ||
* An updated [ | * 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? == | ||
| Line 51: | Line 51: | ||
=== '''Live image''' === | === '''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. | |||
== Test Cases == | == Test Cases == | ||
Provide a list of test areas or test cases that you'd like contributors to execute. For other examples, see [[:Category:Test_Cases]]. | Provide a list of test areas or test cases that you'd like contributors to execute. For other examples, see [[:Category:Test_Cases]]. | ||
== Reporting bugs == | |||
Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day: | |||
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. | |||
== 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.: | |||
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. | |||
{| | {| | ||
! User | ! User | ||
| Line 80: | Line 89: | ||
|} | |} | ||
<!-- remove this comment block when creating a real Test Day | |||
[[Category:Fedora 24 Test Days]] | [[Category:Fedora 24 Test Days]] | ||
--> | |||
<!-- remove this category when creating a test day page --> | <!-- remove this category when creating a test day page --> | ||
[[Category:QA Templates]] | [[Category:QA Templates]] | ||
Revision as of 19:13, 11 April 2016
| Fedora Test Day | |
|---|---|
| |
| FIXME | |
| Date | <<FIXME>> |
| Time | all day |
| Website | QA/Test Days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
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?
Today's instalment of Fedora 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)
- Quality Assurance - Tester1 (irc_nick3), Tester2 (irc_nick4)
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?
- 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 Fedora XX pre-release, or a Fedora XX nightly image
How to test?
High level details on how a contributor can get involved. This can include (but not limited to):
- Areas to target with exploratory testing
- A list of pre-defined test cases to execute
- How to report back results
Here's another common chunk (again, replace XX as above):
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 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 here: please be sure to download one for the correct release.
Test Cases
Provide a list of test areas or test cases that you'd like contributors to execute. For other examples, see Category:Test_Cases.
Reporting bugs
Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
If you have problems with any of the tests, report a bug to Bugzilla usually for the component udisks, or 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.
Test Results
If you use the Test Days app, just explain that users should enter results there and they will be transferred to the page later. For e.g.:
Please enter your results on the <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 result template to enter your result, as shown in the example result line.
| User | Sample test 1 | Sample test 2 | Sample test 3 | Sample test 4 | References |
|---|---|---|---|---|---|
| Sample User |  |
 |
 |