Manual tests for Eclipse plugin

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

Update URI

Eclipse-Java/Groovy

Use Update Manager to get WebSphere sMash plug-ins

• Eclipse Update site

Steps:

1. Install fresh eclipse SDK from http://www.eclipse.org/downloads
2. Click Help>Software Updates>Find and Install..., create a new remote site pointing to the Update URI
3. Select all features
4. Accept license and install all, restart after complete.
5. TEST: Verify that there are no errors or exceptions in the {workspace}/.metadata/.log from the PZ eclipse update. You may see an error dialog indicating that the CLI is not configured. This is normal and should not be reported as a bug.

Configure CLI

• Preferences

Steps:

1. Open Window > Preferences > WebSphere sMash. You may see an error dialog indicating that the CLI is not configured. This is normal and should not be reported as a bug.
2. In the "Zero home" field, enter a directory that contains a CLI.
3. TEST: You should see an error message at the top of the preferences page. The module group combo should be disabled.
4. Now enter the location of a valid CLI in the "Zero home" field. After, the "Loading..." message disappears from the combo, select a module group.
5. TEST: You should see at least one module group in the list.
6. Press OK.

Create a new application and run it

• Eclipse New Wizard
• zero.application.template
• Eclipse Launch configuration

Steps:

1. File>New> WebSphere sMash Application
2. Right-click new project select Run As>WebSphere sMash Application
3. Browse to http://localhost:8080
4. TEST: Verify that a WebSphere sMash Welcome index is displayed
5. Now click Run As>WebSphere sMash Application again without stopping the previous launch
6. TEST: Console message should indicate a port conflict because the port is taken by the other launch

Create a new sample application

• New Sample Project Wizard

Steps:

1. File > New > Example... > WebSphere sMash Sample Application
2. TEST: Upon entering the wizard, you should see a list with a single item that says "Retrieving items from repository...". You should also have a running background job with the title "Repository Search".
3. TEST: When the job finishes, the list will be populated with sample application module names with their corresponding revision.
4. Select one of the items and press Next.
5. TEST: On the next page, the "Project name" field will contain the sample application name.
6. TEST: Press Finish. The project should be created in the workspace.

Export/Import WebSphere sMash application

• Export in shared mode including source and then reimport as project

Steps:

1. Create new WebSphere sMash Application
2. Right-click a Zero project and select Export...>WebSphere sMash>WebSphere sMash Export Wizard
3. TEST: Verify that you get an export dialog like the one shown below:
   
   
4. Change export directory to a directory that is outside the workspace (not under the project directory), check 'Include Source' as shown below, and click OK
   
   
5. TEST: Look in configured export directory to verify that there is a file called projectname-version.zip
6. Delete WebSphere sMash application that you created from the workspace.
7. Click File>Import>General/Existing Projects in Workspace>Select Archive File. Browse for the zip you exported and click OK
8. TEST: Verify that package imports into workspace without any errors (check {workspace}/.metadata/.log)
9. TEST: Run the project as a WebSphere sMash Application and browse to http://localhost:8080.

Standalone Export of Zero Application

• Export in standalone mode and then unzip package and run from command-line

Steps:

1. Create new WebSphere sMash Application
2. Right-click a Zero project and select Export...>WebSphere sMash>WebSphere sMash Export Wizard
3. TEST: Verify that you get an export dialog like the one shown below:
   
   
4. Leave the default export directory, check 'Standalone' as shown below, and click OK.
   
   
5. TEST: Refresh the project directory, verify that projectname-version-all.zip is created in the export directory
6. Unzip package into a new temp directory
7. cd into the directory created
8. Invoke 'zero resolve'
9. Invoke 'zero start'
10. TEST: Verify that console message indicates that application is successfully started on port 8080
11. TEST: Verify that http://localhost:8080 successfully loads in a browser.
12. Invoke 'zero stop'

Repository Management

• Search for new libraries in remote repository
• Add new library from remote repository
• Delete library from local repository

Steps:

1. Click orange repository icon in toolbar to open Repository Management dialog.
2. Type zero in the Organization field and *.demo in the Module field.
3. Press the Search button.
4. TEST: You should see several entries in the right-hand list, all of which have names that end with .demo.
5. Select several of the entries from the right-hand list. Verify that none of the entries already exist in the left-hand list.
6. Press the Download button.
7. TEST: After the download operation finishes, you should see new entries in the left-hand list.
8. Select a few of the .demo entries from the left-hand list. Then press the Remove button.
9. TEST: After the remove operation finishes, the entries you selected should no longer appear in the left-hand list.

Groovy Debug/Global Context Debug view

• Java debugger breaks on breakpoint set in Groovy source
• GlobalContext Debug view shows GC contents

Steps:

1. Create New Zero Application
2. Right click /public source folder and select New>Other...>General>File and type test.groovy for the name
3. Answer yes to add Groovy support to project
4. Copy the following code into test.groovy e.g.:
   println("foo")
event.test = 'new string'
event.test = 'updated string'

5. Save the file
6. Add a break point to the second line of the test.groovy file
7. Right-click Project Debug As>WebSphere sMash Application
8. TEST: Verify console message indicates that application started on port 8080
9. Browse to http://localhost:8080/test.groovy
10. TEST: Verify that breakpoint hit and debugger is suspended at second line of Groovy code
11. TEST: Verify that Global Context debug view is showing in top-right corner as shown below:
    
    
12. TEST: Step to the next line and verify that there is a new node in the GlobalContext debug view called event/test set to "new string"
13. TEST: Step again and verify that the event/test node has changed to "updated string"

<?php
   include "JSONResultHandler.php";
   echo "Hello";
?>