QA:Testcase fpe cloning

Description

This test case tests whether cloning packages from Fedora Git works as expected. In particular, it tests if authenticated, anonymous cloning works as well as projects are added to working sets.

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_cloning
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 eclipse-fedorapackager. In the top area of the wizard, a message should be shown that ~/.fedora.cert has been found and should use the username extracted from it for the SSH based clone. Click "Finish". This will only work if you are a sponsored packager. If you are not sponsored, proceed with anonymous clone tests.
4. Fedora Packager for Eclipse should then ask if you'd like to switch to the "Fedora Packaging" perspective. Choose "Yes".
5. A project with name eclipse-fedorapackager should now be available in your Eclipse workspace.
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 eclipse-rpm-editor as package name.
8. Non-existing package: Repeat steps 2-5 but select "Clone Anonymously" and enter eclipse-123456 as package name. This should result with an error message indicating that package eclipse-123456 does not exist.
9. Add package to working set: Repeat steps 2-5, use package eclipse-changelog and select "Add project to working set". Create a new one, call it testworkingset

Expected Results

1. Cloning should succeed without errors which weren't expected. I.e. it is expected that an error occurs if the Git repository does not exist for the entered package.
2. For the test in step 10 above verify results as follows: In the "Project Explorer" view select the triangular shape as illustrated in the following screenshot. Choose working sets as the top-level-element.
   Then click the triangular icon again and make sure that testworkingset is selected. After that make sure that project eclipse-changelog shows up as part of that working set. All other projects in your current workspace should be hidden.