From Fedora Project Wiki
No edit summary
Line 1: Line 1:
{{QA/Test_Case
{{QA/Test_Case
|description=This test case tests whether pushing scratch builds from local SRPMs to [http://koji.fedoraproject.org Koji] works as expected. <<<FIXME>>>
|description=This test case tests whether pushing scratch builds from local SRPMs to [http://koji.fedoraproject.org Koji] works as expected.
|setup=
|setup=
# Boot into the machine/VM you wish to test
# Boot into the machine/VM you wish to test
Line 6: Line 6:
# 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_local_srpm_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 {{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.
# 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 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".
# 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.
# Edit the .spec file and update the "Release:" field (e.g. increment the value by one) and add a new changelog entry.
# 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.
# {{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.
# {{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.
# 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.  
# Next, we need to create an SRPM in order to be able to use that for the Koji scratch build.
<<<FIXME>>>
|results=
|results=
# <<<FIXME>>>
# On successful Koji build submission you should see messages similar to this: [[Image:KojiBuildPopupMessage.png]]
# On successful Koji build submission 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 {{command|ALT+SHIFT+Q Q}} => "General" => "Error Log"
# 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 in order.
}}
}}

Revision as of 17:00, 21 September 2011

Description

This test case tests whether pushing scratch builds from local SRPMs to Koji works as expected.

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_local_srpm_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 package name of a package you maintain or use package Package-x-generic-16.pngeclipse-fedorapackager. If you use package Package-x-generic-16.pngeclipse-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. Edit the .spec file and update the "Release:" field (e.g. increment the value by one) and add a new changelog entry.
  7. 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.
  8. Back in the .spec file press CTRL+ALT+C, which should add a new changelog stub. Enter "Fedora Packager for Eclipse Test Day" as the message.
  9. Next, we need to create an SRPM in order to be able to use that for the Koji scratch build.

<<<FIXME>>>

Expected Results

  1. <<<FIXME>>>
  2. On successful Koji build submission you should see messages similar to this: KojiBuildPopupMessage.png
  3. 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"
  4. 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.



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