Manual tests for Catalog Zero

Guidelines for documenting the manual tests:

• Summarize the elements covered in the test
• Enumerate the steps (ordered list)
• Call out test points with a TEST bullet
• Include screenshots as appropriate; many of the manual tests will be visual, so screenshots are helpful

Setup

1. Install and configure Catalog Zero and MySql as described in the Developers Guide using Eclipse/SVN
2. TEST: Validate that the steps documented are correct
3. TEST: Verify with all 3 browsers; Mozilla( 2.0+), IE( 7.0+ ) and Safari ( 3.0+ )
4. TEST: Repeat the installation using the Command Line Interface

Create

Tests confirm:

• Ability to create new entries in the Catalog

Steps:

1. Create a Zero application in Eclipse
2. Export the application using the Zero export wizard as a shared (not standalone) ZIP file. 1. Start the zero.catalogApp as a Zero application
3. TEST: Verify that "Add an Entry" does not appear when no user is signed in.
4. Sign in as (userid: johndoe, password: password). Verify that "Add an Entry" does not appear, since "johndoe" is not authorized to upload. Sign out.
5. TEST: Sign in using invalid credentials. Verify that an authentication error is displayed.
6. TEST: Sign in as an authorized user (userid: gregg, password: password). Make sure that "Add an Entry" is showing. Click on "logout" and verify the "Add an Entry" disappears and "[login]" is now an option.
7. TEST: Sign in again as a different authorized user (userid: brett, password: password). Verify that "Add an Entry" is available as an option.
8. Upload the exported ZIP file
9. Catalog looks for an ivy.xml in the zip file. If it exists, verify the following data is extracted:
   • PackageName
   • Description
   • Revision
   • Author
   • Publisher
10. TEST: Verify that Catalog automatically determines the file is a new package and offers the appropriate form
11. TEST: Verify the following fields are displayed and/or editable:
    • Entry creator( owner ) name (read-only - populated from authentication service)
    • Entry summary - prepopulate from package name
    • ivy contents - Click on link ( ivy.xml) and a new window will popup showing the contents of the xml file.
    • Entry description - prepopulate from package description
    • Wiki control
      • Page template includes sample, doc, usage, additional links, screenshots, etc.
    • Extracted thumbnail if present
12. TEST: Click OK. Verify that the package or release is created or updated successfully.
13. TEST: Repeat the upload and verify that the Catalog tells the user to delete the existing package before uploading again.
14. TEST: Repeat tests above with another project.

List view / Home

Tests confirm:

• Items that can be selected from the list view

1. TEST: From the List view / Home, logout and login as an authorized user (userid: brett, password: password). With the items being displayed, select ( click on the name or around the area) the last item that was upload last in previous section, like employee.demo. Verify that the next view is the details view, like below:

Steps:

1. After uploading the 2 packages, verify the following:
2. TEST: Click on "Show Description" link and verify the list gets expanded.
3. TEST: With the list expanded, click the "logout" link. Verify that "[Edit]" and "[Delete] links disappear. Log in again, and the links show re-appear.
4. TEST: With the list expanded again, logout and login as a different user ( gregg ) and verify that "[Edit]" and "[Delete] links disappear. Log in again ( Brett ) and the links should re-appear.
5. TEST: Verify the [Edit] link will bring up the 'Conflict Screen' asking you which one to edit. Verify the 3 links work
6. TEST: Click on the Package name and verify this details form is displayed. Find the "visit count" value ( should be set to one) and remember it. Click on the "Home" link to go back to list
7. TEST: Repeat above step again but this time, verify the "Visit count" should be one more, probably set to two. Click the "Home" link to go back to list.
8. Now export another package ( different package not the 2 previous ones ) using Zero export wizard as a shared (not standalone)
9. Logout and login on as another valid user, like "Gregg" ,"edchat" (password = password).
10. TEST: Once login, upload the package you exported. Click ok to create and the next view should be the listview / home. Verify they there are 2 separate owners and only one can be edited
11. TEST: Test the Search function by searching for a string in the Name field of one or more entries. Verify that the correct results are returned. Click "Show All" or "Catalog Home" to return to the full list.
12. TEST: Test the Search function by searching for a string in the Description field of one of the entries. Verify that the correct results are returned.

Details view / add comments

Tests confirm:

• Detailed view of the packages selected from the list view

1. TEST: From the Detail view, verify the fields, comments, download button, ivy xml button and login / logout .

Steps:

1. Using the previously uploaded package ( like employee.demo ), make sure your on the list view / home page ( if not, click on the "home" link). Click the logout link to logoff.
2. TEST: At the home page, click on the package name in the list ( or around that area ) and verify that the next page is the details page.
3. TEST: Verify the fields have been populated:
   
   • Owner name ( should be edchat )
   • Entry summary
   • Entry description
   • Rating ( not rated so all the stars should be white )
   • Download count ( should be zero )
   • Visit Count ( greater then 0 )
   • Last Update ( date should be when was last uploaded )
   • Version ( 1.0.xxxx )
   • Package Type ( should be set to shared )
4. TEST: Still being logged off, click on the "Prior Release" tab and verify content says "There are no prior releases."
5. TEST: Now click on the "Comments" tab and verify in the comment window at bottom says "Login to add a comment:" Go ahead and sign in as the owner of this package; for employee.demo, was edchat.
6. TEST: After signing in, enter in a comment, like "This is the best package..." and click on "Add Comment" button. Verify the comment was save, is being displayed below and header of comment says Comments : (1).
7. TEST: In the comment area, ( where you added your comment ), click on the "Recommend" link and verify that change to "Recommend (1 )". Do it again and verify is says "Recommend (2 )". Next, click on the "Report Abuse" link and verify text changes to Red.
8. TEST: Click on the "IVY XML" button and verify that a separate window pops up, displaying the contents of the xml file.
9. TEST: Click on the "Download" button and verify that a dialog window pops up, with a title saying "Install Instructions for a Shared Package". Click "ok" and verify the dialog closes and the view is still on the Details page.
10. TEST: Click on the "[Edit]" button and verify the next view is the "Edit Entry". Verify that you can exit this page by clicking on "cancel" and should you you back to previous page, which is the Details page.
11. TEST: Click on the "[Edit]" button again, brings you to "Edit Entry" page again. This time, click on "Ok" button and verify that the next view is the "home page / list view".
12. TEST: From the home view, click on package name or around that area and verify the next view is "details view".
13. TEST: Go back to the home page. Click on the ""home" link and verify that the list view / home page is being played and verify the message that was on the top, "Service xxxxx.xxxx-V1.xxxx.xxx was updated successfully" is now gone and list has been sorted to normal view.
14. This completes the detail view.

Update

Tests confirm:

• Ability to update existing entries in the Catalog

Steps:

1. In Eclipse, update the ivy.xml on a Project Zero application to have a newer revision (e.g. from 1.0.0 to 1.0.1)
2. Export your application using the Zero export wizard as a shared ZIP file (not standalone)
3. From the home page, sign out and sign in as "edchat".
4. TEST: Verify that the "[Edit]" link only shows up for packages where the signed-in user matches the owner. If you use the above sample, Employee.demo owner should be set to edchat.
5. TEST: Click on the package name or around the area and verify it brings you to the next view called "Details view". The title of page should be the name of package, like "employee.demo".
6. Let's get the newer version of the package, the one that was exported. Click on "Add an Entry" link to upload the package and enter in the [package.zip] name ( Browse for the file if you don;t know where you stored it ). Click "ok" to upload file.
7. TEST: Verify that upload detects a new release is to be created under an existing package entry.
8. TEST: Verify that entry creator can update * Entry summary * Entry description * Release changes
9. TEST: Verify there's a prior release, by clicking the "Previous Releases".
10. TEST: Click OK and verify the new view is Home / List view, a message at top states "Service xxxx.xxx-V1.0.1 was created successfully" and "summary changes" are shown under the package name.
11. TEST: Click on package name to go to details view and verify that all updates are made successfully.
12. TEST: Click on "[edit]", version 1.0.1 to edit the package. Verify the next view is "Edit Entry" and the fields that were changed; summary, release changes and description, are being shown correctly in this view. Click "cancel" to come back to the prior page, details view.
13. TEST: Verify that releases can be edited from the Prior Releases; Click on the "Prior Releases" tab and verify that the prior release entry is being display, version 1.0.0.
14. TEST: Click on "[edit]", version 1.0.0 to edit the package. Verify the next view is "Edit Entry" and the fields are from version 1.0.0 NOT from the newer version; summary, release changes and description. Verify they being shown correctly in this view. Click "cancel" to come back to the prior page, details view.
15. TEST: Click "home" link to go back to list view. Click "[edit] to verify that an entry can be edited and that version 1.0.1 is the one being editied
16. TEST: While on the "Edit Entry page", edit the "summary field", "changes field" and "description field" with more text. Click "ok" to save the changes and verify the next view should be the list view. Go back to details view by clicking on the package name and verify the changes to the "summary", "changes" and "description" fields are being reflected in this view.
17. TEST: Go back to the home page. Click on the ""home" link and verify that the list view / home page is being played. This completes the Edit / Updates view.

Rating

Tests confirm:

• Ability to rate the package in the Catalog from 1 to 5 stars

Steps:

1. While back at the list view / home page, logout.
2. TEST: Click on the package name to go to Details view. After the view gets displayed, click on the rating link "not reviewd" and now select the 5 stars. Verify that the sign-on dialog appears after trying to rate it, in this case 5 stars.
3. TEST: Now login as other user "brett" ( password=password ). We'll try to re-rate it. After signing in, click on the "not reviewed" link and select the 5 stars. Verify that NO sign-in dialog appears and that the 5 stars stay selected and wording next to the stars say "1 review".
4. TEST: Go back to list view, by clicking on "home" link and Verify in the list that this package is showing the 5 stars and that its says "1 review".
5. TEST: Do it again, go to details view on the same package you just rated. Logout and log in as another user like "gregg" ( password = password ) and click on the rate link ( 1 review ) and this time, select 1 star. Verify that after selecting the rating, it should mentioned "2 reviews" and the new rating should be the average; in this case is 3 stars ( 5 stars + 1 star / 2) .
6. TEST: Now go back to list view, by clicking on "home" link and Verify in the list that this package is showing the average, which in this case is 3 stars and says "2 reviews".
7. Click the "logout" to sign off and log back in as the original user "Brett"" Verify that the "[edit] and [delete] links reappear for this package. This completes the Rating section.

Downloads

Tests confirm:

• Ability to download entries from the Catalog

Steps:

1. Back on the List view / home, sign in as "Brett" if not already signed in. Verify that the "[edit] and [delete] links appear for the package that was uploaded in the beginning or if you used "Ztest"
2. TEST: Verify that download buttons work in both list views and details view.
3. TEST: Verify that the instructions are correct. Verify that the file can be downloaded by following the instructions.
4. TEST: Verify that prior releases can be downloaded too

Sorting, filtering and flagging

Tests confirm:

• Ability to Sort, filter out certain item(s) and flag favorites

Steps:

1. Go back to list view / home page, if not already there. Login as Brett as we prepare to upload several package that will enable Sorting, Filtering and flagging of favorites.
2. Export a few application(4 or more) using the Zero export wizard as a shared (not standalone) ZIP file. As you create the packages, name one that start off with an 'A', like "A-test". Do the next 3, name package starting off with 'B' and export it. Repeat this step 2 more times. After all the packages have been export, upload them by clicking on "Add an Entry"
3. TEST: After all packages, verify they can be sorted by clicking on the "name" ( in header ) and then try "owner".

Delete

Tests confirm:

• Ability to delete entries in the Catalog

Steps:

1. TEST: Verify that any entry or release that was created by the logged-in user can only be deleted by that user.
2. TEST: Verify that delete works from list view as well as details view.
3. TEST: Verify that delete of prior releases works.
4. TEST: Verify that deleting the final release of an entry deletes the entire entry.