Manual tests for Tutorials, Samples, and Modules

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

Hello Dojo Tutorial

Test confirms:

1. The tutorial application can be built and run as described.

Steps:

1. Read through HelloDojoTutorial, located under samples, and complete each step.

Suggestion Box Tutorial

Test confirms:

1. The "suggestion box application" tutorial can be completed as described. This tutorial can be found in the Developer's Guide under the Samples section. Please use the tutorial associated with the build being tested.

Employee List Sample

Tests confirm:

• Setup instructions
• Operation of the Dojo-based UI

Steps:

1. Install the Employee List example using the CLI instructions
2. Access the UI at http://localhost:8080
3. TEST Confirm page contains empty table, similar to the following
   

1. TEST Click on List Employees and confirm that employees are listed, similar to the following
   

1. Add a new employee:
   1. Click on Create Employee
   2. Confirm page shows panel for creating new entries, similar to the following
      
   3. Enter an employee username, first name, last name, location and phone number.
   4. Click Submit.
   5. TEST Confirm page contains the new entry
2. Edit an employee
   1. Select an employee in the list and click Edit Employee
   2. Change the employee's first name
   3. Click Submit
   4. TEST Confirm the page reflects the change
3. Delete an employee
   1. Select an employee in the list and click Delete Employee
   2. TEST Confirm the page reflects the change
4. Stop the application. Delete the application.
5. Recreate the sample using the AppBuilder instructions.
6. TEST Confirm that the app runs and the page loads.
7. Stop the application. Delete the application.
8. Recreate the sample using the Eclipse instructions.
9. TEST Confirm that the app runs and the page loads.

Employee List with PHP Sample

Tests confirm:

• Setup instructions
• Operation of the Dojo-based UI

Steps:

1. Follow the steps as described above for the Employee List demo using the CLI. Use the zero.phpemployee.demo module name.

Connection API Sample

Tests confirm:

• Setup instructions
• Operation of the connection API tests

Steps:

1. Create and start the sample according to the CLI setup instructions
2. Execute each of the tests.
3. TEST Confirm that the output of each test returns the documented response.

Atom Sample

Tests confirm:

• Setup instructions
• Operation of the Dojo-based UI
• Operation of various feeds

Steps:

1. Create and start the sample according to the CLI setup instructions
2. Access the UI at described in the documentation
3. TEST: Confirm page contains entries, similar to the following
   
4. Add another entry:
   1. Click new
   2. TEST: Confirm page shows panel for creating new entries, similar to the following
      
   3. Enter a title and author
   4. Click save (the default values are fine)
5. TEST: Confirm page contains the new entry
6. Edit an entry:
   1. Click on an entry
   2. Change the title
   3. Click save
   4. Reload the page
7. TEST: Confirm page shows the updated entry
8. Delete an entry:
   1. Click on an entry
   2. Click delete (on the entry)
   3. Reload the page
9. TEST: Confirm the entry no longer appears
10. Access the UI at http://localhost:8080/classics
11. TEST: Confirm that the entries can NOT be edited (no edit or delete button)
12. Access the feed at http://localhost:8080/custom/feeds/books.groovy
13. TEST: Confirm that seven entries are shown
14. Access the feed at http://localhost:8080/biographies/feeds/custom.groovy
15. TEST: Confirm that the three entries have links to george's greeting (select each title)

Flow Samples

Tests confirm:

• Setup instructions
• Operation of the Dojo-based UI

Steps:

1. Create and start the samples according to the CLI setup instructions
2. Follow the instructions to execute each of the tests.
3. TEST: Confirm that the output of each tests match what is documented.

Office Monitor Sample

Tests confirm:

• Setup instructions
• Operation of the Dojo-based UI

Steps:

1. Create and start the sample according to the CLI setup instructions or README file.
2. Ensure zero populateData has been run.
3. Open admin in one window /officemon/admin.html.
4. Open calendar in another window /officemon/index.html
5. TEST admin - ensure 11 users and 3 groups are visible
6. TEST calendar - ensure that the same set of users is visible (may be thru multiple pages)
7. TEST admin - add a user called "Barak"
8. TEST calendar - refresh and ensure Barak appears on the list.
9. TEST calendar - mark Barak "Office AM" (click 3 times for Barak - today cell, and click "ok" in the confirm column) update should fail with "ReadOnly Mode: Change(s) were not saved for Barak. Change Preferences->ReadOnly to allow updates."
10. TEST calendar - click preferences and deselect "read only". Resubmit "ok" in cofirm column and it should work.
11. TEST admin - refresh. Barak should appear out of office.
12. TEST calendar - click on Azelia "today" cell. "Advance edit" dialog should open. Click on the pencil on the "home" message and "Sleep". Click ok, and then Click "ok" in confirm column. Console should show you that changes were saved.

1. TEST calendar - move to next week. ">> week" top right corner. And set an event on any of the users.
2. TEST calendar - click "This Week" button to bring you back to the current week. Refresh and go back to "next week" The user event should be visible.

Flickr Server Side Mashup Sample

Tests confirm:

• Setup instructions
• Operation of the Dojo-based UI

Steps:

1. Create and start the sample according to the CLI setup instructions
2. TEST: Confirm that the application starts and displays correctly
3. TEST: Execute some searches and verify that the results are updated appropriately

OpenID Sample

Tests confirm:

• Setup instructions
• Operation of the Dojo-based UI

Steps:

1. Create and start the sample according to the CLI setup instructions
2. Follow the instructions documented in the sample.
3. TEST: Confirm that the results match the documented screenshots

IWidgets Tutorial

Tests confirm:

• Tutorial instructions

Steps:

1. Follow the setup instructions documented in the tutorial.
2. Follow the steps in the tutorial.
3. TEST: Confirm that the results are as documented.

Kicker and Receiver Sample

Tests confirm:

• Setup instructions
• Operation of the Dojo-based UI

Steps:

1. Create and start the sample according to the CLI setup instructions
2. Follow the instructions for running the application.
3. TEST: Verify that the kicker and receiver tabs behave as expected.

Open AJAX Client Side Mashup

Tests confirm:

• Setup instructions
• Operation of the UI

Steps:

1. Create and start the sample according to the CLI setup instructions
2. Follow the instructions for running the 3rd-party and mashup applications.
3. TEST: Verify that the mashup application correctly consumes data from the 3rd party application.

RTE - Messaging Sample

Tests confirm:

• Setup instructions
• Operation of the UI

Steps:

1. Create and start the sample applications according to the setup instructions
2. Follow the instructions for running the applications.
3. TEST: Verify that the application behaves as documented.

Flickr Mashup Module

Test confirms:

• The ability to connect to and use a 3rd party web service in a Zero application.

Steps:

1. Download and unzip the flickr.test-2.0.0.0.zip:
2. Import the flickr.test project into an Eclipse workspace with an experimental repository and resolve the project.
3. Update the flickr.test/config/zero.config with your Flickr Api Key NOTE: Surround the value with double quotes ("1234567890abcd").
4. Run the flickr.test as a Project Zero Application.
5. Access the UI at http://localhost:8080
6. TEST that the application looks like the screenshot above.
7. Check out the zero.flickr.tests module from trunk in SVN
8. Resolve the module
9. Run zero.flickr.tests as a JUNIT test
10. TEST that all tests pass.

Amazon ECS Module

Test confirms:

• Operation of the module

Steps:

1. In a CLI pointing to the experimental repo, create a new Zero app called "TestAmazon"
2. Add "zero.amazon.ecs" as a dependency in the app's ivy.xml
3. Configure an access key as described in the instructions, here:
4. Create a file called "test.groovy" in the "public" directory
5. Paste in the sample code from the "Performing a search" section in the instructions
6. Start the application
7. Browse to http://localhost:8080/test.groovy
8. TEST that an XML file is returned with books about Harry Potter

Fire PHP Module

Test confirms:

• Operation of the module

Steps:

1. TEST - confirm the instructions on the blog post, here: FirePHP

Wikipedia Module

Test confirms:

• Operation of the module

Steps:

1. From a CLI pointing to the experimental repo, execute zero create zero.services.wikipedia from zero:zero.services.wikipedia
2. From the zero.services.wikipedia directory, execute zero start
3. From a web browser, browse to http://localhost:8080/resources/wikipedia/IBM
4. TEST that the wikipedia page for IBM is returned.

zero.admin using CLI

Tests confirm:

• Setup instructions
• Operation of the Dojo-based UI [starting, stoping, monitoring, adding, and removing apps]

Steps:

1. Execute CLI command: zero create myzeroadmin from zero:zero.admin
2. Change to the project's root directory: cd myzeroadmin
3. Execute CLI command: zero start
4. TEST Access the UI at http://localhost:9072 to make sure its running
5. Create a new app if you dont have any existing apps: zero create testapp1
6. TEST Add an existing app to the list per the instructions on http://localhost:9072
7. TEST Start an app by clicking on the green arrow
8. TEST Click on the app link to access the app [verify that the app is functioning as expected]
9. TEST Stop the app by clicking the red box, then refresh [verify that the app has been stopped successfully]
10. TEST Remove the app from the list by clicking on the yellow X
11. TEST Start/Stop the app using the CLI and refresh to ensure that the status is reflected properly

• flickr.test-2.0.0.0.zip: New Flickr Test