No edit summary |
No edit summary |
||
Line 20: | Line 20: | ||
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) | ||
* Quality Assurance - [[User:Martix|Martin Holec]] (Martix), [[User:Vhumpa|Vítězslav Humpa]] (vhumpa), [[User:Adamwill|Adam Williamson ( | * Quality Assurance - [[User:Martix|Martin Holec]] (Martix), [[User:Vhumpa|Vítězslav Humpa]] (vhumpa), [[User:Adamwill|Adam Williamson (adamw)]] | ||
== Prerequisite for Test Day == | == Prerequisite for Test Day == | ||
Line 31: | Line 31: | ||
* Free space on HD | * Free space on HD | ||
* An updated [http://fedoraproject.org/get-prerelease Fedora F18 pre-release] or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ nightly live image] | |||
* An updated [http://fedoraproject.org/get-prerelease Fedora | |||
* Your hardware profile uploaded to [http://www.smolts.org Smolt] according to [http://smolts.org/smolt-wiki/Main_Page#Usage these instructions] | * 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? == | == How to test? == | ||
This Test Day has two parts. First part is covered by test cases and it's focused on initial setup and getting you familiar with basic functionality. Second is exploratory testing when you are free to use software how do you like. Don't worry and try to break Gnome in various ways which you expect to work. | |||
=== '''Update your machine''' === | === '''Update your machine''' === | ||
If you're running Fedora | If you're running Fedora F18, make sure you have all the current updates for it installed, using the update manager. Or: | ||
=== '''Live image''' === | === '''Live image''' === | ||
Optionally, you may download a non-destructive | Optionally, you may download a non-destructive 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]. | ||
== Test Cases == | == Test Cases == |
Revision as of 15:44, 31 October 2012
Fedora Test Days | |
---|---|
Gnome 3.6 | |
Date | 2012-11-08 |
Time | all day |
Website | QA/Fedora_18_test_days |
IRC | #fedora-test-day (webirc) |
Mailing list | test |
What to test?
Today's instalment of Fedora Test Day will focus on Gnome 3.6.
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 - Martin Holec (Martix), Vítězslav Humpa (vhumpa), Adam Williamson (adamw)
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
- An updated Fedora F18 pre-release or a nightly live image
- Your hardware profile uploaded to Smolt according to these instructions
How to test?
This Test Day has two parts. First part is covered by test cases and it's focused on initial setup and getting you familiar with basic functionality. Second is exploratory testing when you are free to use software how do you like. Don't worry and try to break Gnome in various ways which you expect to work.
Update your machine
If you're running Fedora F18, make sure you have all the current updates for it installed, using the update manager. Or:
Live image
Optionally, you may download a non-destructive live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here.
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.
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:
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. 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, use the result template to enter your result, as shown in the example result line.
User | Smolt Profile | Sample test 1 | Sample test 2 | Sample test 3 | Sample test 4 | References |
---|---|---|---|---|---|---|
Sample User | HW |