2011-10-13 Fedora Packager for Eclipse

Fedora Test Days

Fedora Packager for Eclipse 0.2

Date	2011-10-13
Time	all day

Website	Fedora Packager for Eclipse
IRC	#fedora-test-day (webirc)
Mailing list	test

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 Trac, 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 installment of Fedora Test Day will focus on Fedora Packager for Eclipse

Yay, Fedora Packager for Eclipse 0.2 is out!
As 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 version, its 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 - Andrew Robinson (arobinso), Andrew Overholt (overholt), Alexander Kurtakov (akurtakov)

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
Some test cases require that you are a sponsored Fedora packager (i.e. you maintain some Fedora packages). If you are not sponsored yet, we still appreciate tests feedback for tests which do not require for you to be sponsored.

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:

eclipse-platform-3.7.0-1.3.fc16
eclipse-fedorapackager-0.2.1-1.fc16

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.

Planned Tests

Note
Please note that you may need to use sudo yum install --enablerepo=updates-testing eclipse-fedorapackager-0.2.1-1.fc16 in order to get Fedora Packager for Eclipse 0.2 installed throughout test cases below.

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

If you have problems with any of the tests, try and report a bug. Fedora Packager for Eclipse bugs should be reported to Fedora Packager for Eclipse Trac. You will need a FAS account to report bugs for Fedora Packager for Eclipse. Creating one is easy, and we will help you do this if you ask in IRC.

If you are not sure of the appropriate component, please check in IRC before filing, there are many possibilities. 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 describe your result, following the examples in the Sample user row.

User	Smolt Profile	Upgrade	SSH setup	Cloning	Upload sources	Fedora RPM project	Prep	Local build	Mock builds	Koji builds	Koji SRPM scratch	SRPM import	Debug logging	Bodhi update	References
Sample User	HW	none	pass	none	pass	pass	none	pass	none	pass	pass	pass	warn ^[1]	fail ^[2]	↑ Test pass, but also encountered `eclipse-fedorapackager ticket#98` ↑ `eclipse-fedorapackager ticket#99`
rgrunber	HW	pass	pass	pass	none	fail ^[1]	fail ^[2]	fail ^[3]	pass	none	warn ^[4]	none	pass	none	↑ The option "Fedora RPM Project" was not available from the project menu in the Fedora Packager perspective. ↑ "Prepare Sources for Build" not in context menu ↑ "Build For local Architecture" not in context menu ↑ "Create SRPM" not in context menu. Regular scratch build succeeded.
Andrew Overholt	x86_64 F16 VM on x86_64 F15 host	pass	pass	pass	none	none	none	none	none	none	none	none	none	none
Sami Wagiaalla	x86_64 F16 VM on x86_64 F15 host	pass	none	none	none	none	none	none	none	none	none	none	none	none

[1] Test pass, but also encountered eclipse-fedorapackager ticket#98

[2] eclipse-fedorapackager ticket#99

[3] The option "Fedora RPM Project" was not available from the project menu in the Fedora Packager perspective.

[4] "Prepare Sources for Build" not in context menu

[5] "Build For local Architecture" not in context menu

[6] "Create SRPM" not in context menu. Regular scratch build succeeded.

[1]

[2]

[1]

[2]

[3]

[4]

Search

Test Day:2011-10-13 Fedora Packager for Eclipse

Contents