From Fedora Project Wiki

No edit summary
No edit summary
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{QA/Test_Case
{{QA/Test_Case
|description=This test case tests whether pushing builds to [http://koji.fedoraproject.org Koji] works as expected. Tests include SRPM-based scratch builds and scratch builds. If you have a package which you'd need to push an actual Koji build for, you may test that as well.
|description=This test case tests whether pushing builds to [http://koji.fedoraproject.org Koji] works as expected. Depending on the tester, this will include scratch builds and regular builds. We welcome testers who have a package for which they'd need to push a regular Koji build (e.g. updating a package).
|setup=
|setup=
# Boot into the machine/VM you wish to test
# Boot into the machine/VM you wish to test
# Ensure the {{package|eclipse-fedorapackager-0.2.1-1.fc16}} package '''IS''' installed. Install it via {{command|yum install eclipse-fedorapackager-0.2.1-1.fc16}}.
# Ensure the {{command|eclipse-fedorapackager-0.2.1-1.fc16}} package '''IS''' installed. Install it via {{command|yum install eclipse-fedorapackager-0.2.1-1.fc16}}.
# Make sure that file {{command|~/.fedora.cert}} exists and your FAS SSH key is properly set up in Eclipse and the public key properly uploaded to the FAS account system.
# Make sure that file {{command|~/.fedora.cert}} exists and your FAS SSH key is properly set up in Eclipse and the public key properly uploaded to the FAS account system.
|actions=
|actions=
# Open Eclipse and use a new workspace. {{command|eclipse -data test_day_20111013_fpe_koji_builds}}
# Open Eclipse and use a new workspace. {{command|eclipse -data test_day_20111013_fpe_koji_builds}}
# Press {{command|CTRL+ALT+F I}} to open the import wizard. Alternatively press {{command|CTRL+3}} and start typing "Projects from Fedora Git", then press return.
# Press {{key_press|Ctrl|Alt|F}} {{key_press|I}} to open the import wizard. Alternatively press {{key_press|Ctrl|3}} and start typing "Projects from Fedora Git", then press return.
# Enter the package name of a package you maintain or use package {{package|eclipse-fedorapackager}}. If you use package {{package|eclipse-fedorapackager}} make sure to clone anonymously by selecting the appropriate checkbox and click "Finish".
# Enter the name of a package you maintain or use package {{package|eclipse-fedorapackager}}. If you use package {{package|eclipse-fedorapackager}} make sure to clone anonymously by selecting the appropriate checkbox and click "Finish".
# The package you've just cloned should show up in your workspace
# The package you've just cloned should show up in your workspace
# Expand the project you've cloned into your workspace and double-click the .spec file in it. The .spec file should open in the editor.
# Expand the project you've cloned into your workspace and double-click the .spec file in it. The .spec file should open in the editor.
# Right-click in the .spec file and select "Fedora Packager" => "Perform Scratch Build", alternatively press {{command|CTRL+ALT+F X}} with the .spec file open in the Eclipse editor view. This will check if there are un-pushed changes on the current local branch (i.e. may prompt for SSH passphrase) and will push a scratch build to Koji.
# Koji scratch build: Right-click in the .spec file and select "Fedora Packager" => "Perform Scratch Build", alternatively press {{key_press|Ctrl|Alt|F}} {{key_press|X}} with the .spec file open in the Eclipse editor view. This will check if there are un-pushed changes on the current local branch (i.e. may prompt for SSH passphrase) and will push a scratch build to Koji.
# Next, we test SRPM-based scratch builds. Edit the .spec file and update the "Release:" field (e.g. increment the value by one) and add a new changelog entry.
# Regular Koji build (optional): If you have a package which needs updating, update the .spec file, make sure that changes have been pushed and then push a regular build. Right-click in the .spec file and select "Fedora Packager" => "Push Build to Koji" or alternatively press {{key_press|Ctrl|Alt|F}} {{key_press|K}}.
# {{command|CTRL+3}}, start typing "Changelog", select "Preferences (Changelog)" from the list and press return. Make sure your name and email is correctly set up in the preferences. Press OK to save preferences.
# Back in the .spec file press {{command|CTRL+ALT+C}}, which should add a new changelog stub. Enter "Fedora Packager for Eclipse Test Day" as the message.
# First, we need to create an SRPM from our .spec file.  
|results=
|results=
# On successful Koji build pushes you should see messages similar to this: [[Image:KojiBuildPopupMessage.png]]
# On successful Koji build pushes you should see messages similar to this: [[Image:KojiBuildPopupMessage.png]]
# Moreover, there should be an entry in the Eclipse error log detailing the URL to the task ID. You can show the Error Log view by {{command|ALT+SHIFT+Q Q}} => "General" => "Error Log"
# Moreover, there should be an entry in the Eclipse error log detailing the URL to the task ID. You can show the Error Log view by {{key_press|Alt|Shift|Q}} {{key_press|Q}} => "General" => "Error Log". Note that the Error Log view is part of PDE, which means you'd have to have {{command|eclipse-pde}} installed.
# Clicking the link as provided in the message dialog, should show the familiar Koji Web interface. Make sure user data and other task specific information is in order.
# Clicking the link as provided in the message dialog, should show the familiar Koji Web interface. Make sure user data and other task specific information is as expected.
}}
}}

Latest revision as of 02:03, 29 September 2011

Description

This test case tests whether pushing builds to Koji works as expected. Depending on the tester, this will include scratch builds and regular builds. We welcome testers who have a package for which they'd need to push a regular Koji build (e.g. updating a package).

Setup

  1. Boot into the machine/VM you wish to test
  2. Ensure the eclipse-fedorapackager-0.2.1-1.fc16 package IS installed. Install it via yum install eclipse-fedorapackager-0.2.1-1.fc16.
  3. Make sure that file ~/.fedora.cert exists and your FAS SSH key is properly set up in Eclipse and the public key properly uploaded to the FAS account system.

How to test

  1. Open Eclipse and use a new workspace. eclipse -data test_day_20111013_fpe_koji_builds
  2. Press Ctrl+Alt+F I to open the import wizard. Alternatively press Ctrl+3 and start typing "Projects from Fedora Git", then press return.
  3. Enter the name of a package you maintain or use package eclipse-fedorapackager. If you use package eclipse-fedorapackager make sure to clone anonymously by selecting the appropriate checkbox and click "Finish".
  4. The package you've just cloned should show up in your workspace
  5. Expand the project you've cloned into your workspace and double-click the .spec file in it. The .spec file should open in the editor.
  6. Koji scratch build: Right-click in the .spec file and select "Fedora Packager" => "Perform Scratch Build", alternatively press Ctrl+Alt+F X with the .spec file open in the Eclipse editor view. This will check if there are un-pushed changes on the current local branch (i.e. may prompt for SSH passphrase) and will push a scratch build to Koji.
  7. Regular Koji build (optional): If you have a package which needs updating, update the .spec file, make sure that changes have been pushed and then push a regular build. Right-click in the .spec file and select "Fedora Packager" => "Push Build to Koji" or alternatively press Ctrl+Alt+F K.

Expected Results

  1. On successful Koji build pushes you should see messages similar to this:
  2. Moreover, there should be an entry in the Eclipse error log detailing the URL to the task ID. You can show the Error Log view by Alt+⇧ Shift+Q Q => "General" => "Error Log". Note that the Error Log view is part of PDE, which means you'd have to have eclipse-pde installed.
  3. Clicking the link as provided in the message dialog, should show the familiar Koji Web interface. Make sure user data and other task specific information is as expected.



Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_fpe_koji_builds&oldid=255203"