No edit summary |
|||
| Line 28: | Line 28: | ||
== Prerequisite for Test Day == | == Prerequisite for Test Day == | ||
* An updated [http://fedoraproject.org/get-prerelease Fedora 16 pre-release | * An updated [http://fedoraproject.org/get-prerelease Fedora 16 pre-release] (physical machine or virtual machine), or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ nightly live image] | ||
* 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] | ||
Revision as of 14:19, 30 August 2011
| Fedora Test Days | |
|---|---|
| |
| Fedora 16 Eclipse Indigo Stack | |
| Date | <<FIXME>> |
| Time | all day |
| Website | Features/EclipseIndigo https://fedorahosted.org/eclipse-fedorapackager/ |
| 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 Fedora Packager for Eclipse and the Fedora Eclipse Indigo Stack
As Eclipse 3.7.1 and Fedora Packager for Eclipse 0.2 has been released recently, today's test day can provide a nice way for you to get familiar with the new versions, their looks and all the important functionality - especially if you are new to them.
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Severin Gehwolf (jerboaa), Andrew Robinson (arobinso), Andrew Overholt (overholt), Alexander Kurtakov (akurtakov)
- Quality Assurance - Tester1 (irc_nick3), Tester2 (irc_nick4), Tester3 (irc_nick5)
Prerequisite for Test Day
- An updated Fedora 16 pre-release (physical machine or virtual machine), or a nightly live image
- Your hardware profile uploaded to Smolt according to these instructions
How to test?
- You will either need a physical machine or a virtual machine running a pre-release of Fedora 16
- Make sure that your system is up-to-date. You can update your system using the update manager.
- In particular, you should have the following packages installed:
<<<FIXME>>>
Update your machine/VM to Fedora 16
If you are already running Fedora 16 on your physical machine or in a VM make sure to update your system to the latest packages using the update manager. If you don't have the pre-release of Fedora 16 yet, install Fedora 16 Beta and then update to the latest packages. You may also use the live image for our tests (see below)
Live image
Optionally, you may download a non-destructive F16 live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here.
Perform testing
Please perform as many of the test cases listed as you have the time and the resources to complete, and fill out your results in the table below. You do not need a Fedora account to fill in the table.
Fedora Packager for Eclipse 0.2
- QA:Testcase_fpe_upgrade
- QA:Testcase_fpe_srpm_koji_build
- QA:Testcase_fpe_srpm_import
- QA:Testcase_fpe_debug_logging
Fedora 16 Eclipse Indigo Stack
Unplanned testing
As well as running the formal test cases, you can help simply by using Fedora's Eclipse Indigo stack, including Fedora Packager for Eclipse 0.2 and report any problems you come across in the course of your typical use, even if they do not match up with any of the test cases. If unsure if something is a bug feel free to ask in #fedora-test-day.
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 |  |
 |
 |