From Fedora Project Wiki

No edit summary
No edit summary
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}}
# Open Eclipse and use a new workspace. {{command|eclipse -data test_day_20111013_fpe_cloning}}
#  
# Press {{command|CTRL+ALT+F I}} to open the import wizard
# If you've never used Eclipse for SSH based cloning you will likely not have SSH preferences set up. This might cause some clone failures, but should give you appropriate error messages with proposed fixes. Should you run into this problem, detailed instructions are [https://fedoraproject.org/wiki/Fedora_Packager_For_Eclipse_User_Guide#Configure_SSH_in_Eclipse here]. Feedback is very welcome if error messages are not what you would expect. In fact, this is one test case we'd like to have tested.
# Enter the package name {{package|eclipse-fedorapackager}}. In the top area of the wizard, a message should be shown that a ~/.fedora.cert has been found and should use the username for the SSH based clone. Click "Finish".
# Fedora Packager for Eclipse should then ask if you'd like to switch to the "Fedora Packaging" perspective. Choose "Yes".
# The perspective should open and you should see local branches "f13"-"f16" in the "Git Repositories View"
# Anonymous clone: Repeat steps 2-5 but select "Clone Anonymously" and enter {{package|eclipse-rpm-editor}} as package name.
# Non-existing package: Repeat steps 2-5 but select "Clone Anonymously" and enter {{package|eclipse-123456}} as package name. This should result with an error message indicating that package {{package|eclipse-123456}} does not exist.
|results=
|results=
# <<<FIXME>>>
# Cloning should succeed without un-expected errors. I.e. it is expected that
}}
}}

Revision as of 15:46, 7 September 2011

Description

This test case tests whether cloning packages from Fedora Git works as expected. In particular, authenticated and anonymous cloning works.

Setup

  1. Boot into the machine/VM you wish to test
  2. Ensure the Package-x-generic-16.pngeclipse-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_cloning
  2. Press CTRL+ALT+F I to open the import wizard
  3. If you've never used Eclipse for SSH based cloning you will likely not have SSH preferences set up. This might cause some clone failures, but should give you appropriate error messages with proposed fixes. Should you run into this problem, detailed instructions are here. Feedback is very welcome if error messages are not what you would expect. In fact, this is one test case we'd like to have tested.
  4. Enter the package name Package-x-generic-16.pngeclipse-fedorapackager. In the top area of the wizard, a message should be shown that a ~/.fedora.cert has been found and should use the username for the SSH based clone. Click "Finish".
  5. Fedora Packager for Eclipse should then ask if you'd like to switch to the "Fedora Packaging" perspective. Choose "Yes".
  6. The perspective should open and you should see local branches "f13"-"f16" in the "Git Repositories View"
  7. Anonymous clone: Repeat steps 2-5 but select "Clone Anonymously" and enter Package-x-generic-16.pngeclipse-rpm-editor as package name.
  8. Non-existing package: Repeat steps 2-5 but select "Clone Anonymously" and enter Package-x-generic-16.pngeclipse-123456 as package name. This should result with an error message indicating that package Package-x-generic-16.pngeclipse-123456 does not exist.

Expected Results

  1. Cloning should succeed without un-expected errors. I.e. it is expected that