Manual tests for App Builder

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

Notes

• We need to test App Builder with sMash DE on a combination of platforms (Windows, Mac, Linux) and browsers (FF 2, FF 3).
• Testers should watch for layout problems throughout. For example, truncated windows, misaligned titles, etc. Open bugs to report these defects; these bugs should block bug 4944.

Installing and running App Builder

Install the sMash DE CLI, then execute appbuilder open from the command line. That command also launches Firefox; if you're going to test another browser, then close Firefox and open the other browser to http://localhost:8070.

"My Applications" Tests

NOTE:

• It is presumed that the following tests occur in the order shown. Some tests are based on the result of a prior test, so as to minimize otherwise repetitive steps. Where assumptions of this nature are made, these assumptions are explicitly stated.

New Application

1. Browse to the App Builder http://localhost:8070
2. Click Create new application
3. Enter an application name, e.g. testapp
4. "Creating Application" progress indicator should appear for about 30 seconds
5. TEST The new application should show up in the list, and the focus should be on the application name, hit the enter key to edit the application.
6. TEST You should be taken to the application edit screen. The application name should appear near the top, alongside "My Applications" and "My Repository".
7. TEST You should see a list of files on the left. When you click one of them, it should open in the code editor.
8. TEST Open the Dependencies tab. You should see a list of dependencies including one that looks like "zero:zero.core".
9. TEST Open the Explorer tab. You should see a tree view on the left that shows files. When you click one of them, it should open in the code viewer. Note that this is a read-only view so the file is not editable.

Copy from Repository (Create Employee Demo)

1. From the "My Applications" screen, click "Create from Repository".
2. Enter .demo into the org:module filter, select zero:zero.employee.demo, then click "Create".
3. "Creating Application" progress indicator should appear for about 30 seconds
4. TEST The new application should show up in the list, and the focus should be on the application name, hit the enter key to edit the application.
5. TEST You should be taken to the application edit screen which should show the text "employee.demo" at the top.
6. TEST Open the Console tab and then click Command Prompt. At the "command>" prompt, enter the following command (without the quotes): "zero runsql setup_db.sql". Then press Enter. You should then see some output indicating that the command was successful.
7. TEST Now click the Start link near the top of the page. You should see a "Starting the application" message.
8. TEST When the app has started, the Open in browser link will be enabled, click that link.
9. TEST A new browser window will open and you should see an empty table with several buttons underneath.
10. TEST Pressing the List Employees button should then populate the table with some employee data.
11. TEST Now click the Stop link near the top of the page. Verify that the application is terminated in the browser.

Application List Behavior

1. You should now have two applications in the IDE. Click My Applications to navigate back to the application list.
2. TEST Verify that the sort order changes when you click the Name link.
3. TEST Verify that the application can be edited by clicking either the application name or the Edit icon (pencil) on the right hand side.
4. TEST Verify that an application can be run by clicking the Start icon (green circle). The application entry should now show a red square where it used to show a green circle.
5. TEST Verify that the sort order changes when you click the Status link.
6. TEST Verify that the application you ran previously can be stopped by clicking the Stop icon (red square). The application entry should now show a green circle and the application should be stopped.

Package the Employee Demo Application that was copied from the Repository in the previous test

1. Click on the Package icon for the employee.demo application.
2. TEST The "Package Application" dialog appears.
3. TEST Click the "Package" button. You should be presented with a standard browser Download prompt.
4. TEST Click the browser option to indicate that you wish to "Save" the package (zip file) to your machine. Note: Dependig on your browser settings, you may be asked to select the target directory and/or file name.
5. TEST Verify that package (zip file) was successfully downloaded to the target directory/filename specified.

Import the Employee Demo Application that was Packaged in the previous test

1. (Failure Case) From the My Applications screen, click Import application.
2. TEST The "Import Application" dialog appears.
3. TEST Click the "Browse" button and when prompted, locate and select the employee.demo zip file that was saved in the previous test.
4. TEST Enter the server application "Root Directory" you wish to Import the Application to. Enter the Same Directory that the application had been exported "From" in the previous test.
5. TEST Click the "Import" Button and verify that you are presented with an Error indicating that an Application of that name already exists in the specified target directory.
6. (Success Case) From the My Applications screen, click Import application.
7. TEST The "Import Application" dialog appears
8. TEST Click the "Browse" button and when prompted, locate and select the employee.demo zip file that was saved in the previous test.
9. TEST Enter the server application "Root Directory" you wish to Import the Application to. Enter a Different directory where an application of this name does not currently exist (alternatively: enter a NonExisting Directory).
10. TEST Click the "Import" Button and verify that the Application Manager List is refreshed and that the newly imported application displays in the list with the target directory you entered.

Copy the Employee Demo Application that (the target of the Copy from Repository test above)

1. Click on the Copy Application icon for the employee.demo application
2. TEST The "Copy Application" dialog appears.
3. TEST Verify that the target application Name reads: CopyOfemployee.demo (this is the default target naming - do not change)
4. TEST Click the Copy Button - You should see a progress notification indicating that the employee.demo application will be copied to CopyOfemployee.demo
5. TEST When the Copy completes, you should be presented with a notification of its success. Click OK. The Application List should refresh and the application CopyOfemployee.demo should be visible in the Application List.

Move/Rename the CopyOfemployee.demo Application created in the previous Test

1. Click on the Move/Rename icon for the CopyOfemployee.demo application (target of copy in the previous test).
2. TEST The "Move/Rename Application" dialog appears.
3. TEST Enter RenamedCopyOfemployee.demo in the 'Name:' field and click the Move/Rename button.
4. TEST You should see a progress notification indicating the rename operation that is being performed.
5. TEST When the Rename completes, you should be presented with a notification of its success. Click OK. The Application List should refresh and the application RenamedCopyOfemployee.demo should be visible in the Application List.

Delete the Application that was renamed in the previous Test

1. Click on the Delete icon for the RenamedCopyOfemployee.demo application (target of rename in the previous test).
2. TEST The "Delete Application" dialog appears asking you to confirm your intent to delete the application.
3. TEST Verify that the option "Also delete the application directory" is checked
4. TEST Click the "Yes" Button to confirm the Delete.
5. TEST Verify that Application List is refreshed on completion and that the RenamedCopyOfemployee.demo application does not appear in the Application list.

IDE Application Tests

File Editor tab - Code Editor

1. From the My Applications screen, create a new application and edit it.
2. TEST Verify that the Recent Files list is blank. Verify that the All Files list contains ivy.xml, zero.config, and some others. Verify that no error messages are displayed.
3. TEST Click the zero.config file. Verify that the code editor opens and the file content is displayed. Verify that the Recent Files list now contains zero.config.
4. TEST Verify that the code editor displays correct line numbers to the left of the file contents.
5. TEST scroll to the bottom of the file and verify scrolling behaves correctly, and Go to line function works.
6. TEST Click the details link in the All Files view and verify that the paths to the files are displayed. Now click list and verify that the paths are no longer displayed.
7. TEST Verify that the path (including filename) is displayed in the right side of the editor toolbar.
8. TEST Verify Java JS HTML PHP GT Groovy SQL INI Config XML syntax highlighting
9. TEST Place the cursor inside a code block that is delimited by curly braces. You should see a range indicator to the left of the line numbers which shows the lines that are occupied by the code block.
10. TEST Place the cursor inside a code block that is delimited by parentheses. You should see a highlighting box around the left and right parentheses.
11. TEST edit the file, checkpoint the file, edit the file again, restore the checkpoint and verify the contents are correct
12. TEST undo the checkpoint and edits and verify undo function is correct.
13. TEST redo the checkpoint and edits and verify redo function is correct.
14. TEST reload the page and verify the file editor come up again with the same content
15. TEST verify undo/redo state is gone (buttons grayed out), but checkpoint/restore should still work
16. TEST Create a new file named test.txt. The code editor should open with blank code and 1: on the first line.
17. TEST add and delete some lines verify line numbers are correct
18. TEST switch back to the previous file by clicking it on the recent list, cursor position should be remebered from when you switched out.
19. TEST Rename the file (double click it in the All Files view), verify name is updated in toolbar correctly
20. TEST verify the file content and name outside of the IDE.
21. TEST Copy the file (hover over, then click the "copy" icon in the All Files view), verify file is copied
22. TEST Delete the open file (hover over, then click the X icon in the All Files view), verify editor is closed when deleted

Running the application

1. Click the Start button, near the upper-right corner.
2. TEST Verify that the Start button changes to a Stop button.
3. Click the link to the left of the Stop button.
4. TEST Verify that a new browser tab/window appears and the application home page is loaded.
5. TEST In My Applications, verify that the application entry shows the red icon (represents a stop button).
6. Go back into the application editor. Click Stop.
7. TEST Verify that the Stop button becomes a Start button.
8. TEST Verify that the link to the left of the Start button is disabled.
9. TEST In My Applications, verify that the application entry shows the green "start" icon.
10. TEST Refresh the web browser open to the application home page and verify the browser shows the page is unreachable.

Dependencies tab

1. Click the Dependencies tab.
2. TEST Verify that the dependencies list looks correct. Compare the entries with the contents of config/ivy.xml.
3. TEST Click the Add button and verify that you can add a dependency. Once the operation is complete, the new item should display in the list. Verify the contents of config/ivy.xml.
4. TEST Select an item in the list and click the Remove button. Verify that the item disappears from the list. Verify the contents of config/ivy.xml.
5. TEST Click the Add button. In the dialog, click the Manage Repository button. Verify that a dialog comes up and displays the local repository contents.
6. TEST Type zero into the Organization field and click Search. Verify that some items show up in the list.
7. TEST Select one of the items in the right side list and click the << button. Verify that the item shows up in the list on the right. Note that you should not select an item that already exists locally.
8. TEST Close this dialog and verify that the Add Dependency dialog list now contains the item you downloaded in the previous step.

Explore tab

1. Click the Explore tab
2. TEST verify the file tree contents look correct, and no error messages are displayed.
3. TEST click on various files and verify the Code Viewer is opened and the file contents look correct and the file path is displayed correctly on the right side of the editor.
4. TEST Verify that Show Dependencies is unchecked by default.
5. TEST Toggle the Show Dependencies checkbox. Verify that the tree view changes for each click. In general, the tree should be larger for checked than unchecked.
6. TEST Select a file from the current app. Verify that all buttons are enabled except for Promote.
7. TEST Select a subdirectory. Click on New File and verify that a the create dialog is prepopulated with that subdirectory. Verify that a new file can be created as expected. Change to the File Editor and verify that the new file is listed in the All Files list.
8. TEST Select a subdirectory. Click on New Directory and verify that the create dialog is prepopulated with that subdirectory. Verify that a new directory can be created as expected.
9. TEST In the File Editor, select a file for editing. Switch to the File Explorer. Select the same file and click Delete. Verify that that the file is deleted as expected. Verify that the view of the browsed file is closed. (bug) Click on the File Editor. Verify that the file is removed from the All Files list as well as the Recent Files list. Verify that the file is closed if it had been opened for editing.
10. TEST Select a file and click Copy. Enter a new name. Verify that the copy works as expected. Verify that the All Files list of the App Editor is updated as expected.
11. TEST Select a file and click Move or Rename. Enter a new name. Verify that the file is renamed. Verify that the Recent Files and All Files list of the File Editor is updated as expected.
12. TEST Select a file and click Move or Rename. Enter a new directory. Verify that the file is moved. Verify that the Recent Files and All Files list of the File Editor is updated as expected (path info in tooltips and expanded view).
13. TEST Select a file and click Edit. Verify that the view is switched to the File Editor tab and the file is loaded into the appropriate editor. Edit the file. Switch back to the File Explorer. Verify that the view is refreshed.
14. TEST In the File Editor, select a file for editing. Switch to the File Explorer. Select the same file to open it up in the view window. Select the file's parent directory and click Delete. Verify that that the directory is deleted as expected. Verify that the view of the browsed file is closed. Click on the File Editor. Verify that the appropriate files are removed from the All Files list as well as the Recent Files list. Verify that the previously opened file from that directory is closed.
15. TEST Select a direcgtory and click Copy. Enter a new name. Verify that the copy works as expected. Verify that all files are duplicated in the new directory. Verify that the All Files list of the App Editor is updated as expected.
16. TEST Select a directory and click Move or Rename. Enter a new name. Verify that the directory is renamed. Verify that the Recent Files and All Files list of the File Editor is updated as expected.
17. TEST Select a directory and click Move or Rename. Enter a new directory. Verify that the directory is moved. Verify that the Recent Files and All Files list of the File Editor is updated as expected (path info in tooltips and expanded view).
18. TEST Select Show Dependencies. Click on a file from a dependency. Verify that the Promote button is enabled and the Delete, Copy, Move or Rename, and Edit buttons are disabled. Click on Promote. Verify that the file is promoted. Click on the File Editor. Verify that the All Files list is updated appropriately.
19. TEST Verify that "File Upload" uploads a file to the specified location.
20. TEST (Failure case) Repeat the upload (same file; same target directory); verify a failure message.

IDE Autobuild Tests

Compile when Java file changes

1. In a new application, create a new file /java/Test.java.
2. Enter the following text into the file:

   import zero.core.context.GlobalContext;
   public class Test {
      public void test() {
         GlobalContext.zget("/config/name");
      }
   }

3. TEST View the build-log (accessible below the edit pane; raise the splitter bar to see it) and verify that a successful compile command executed. You should see a message like "Command compile was successful".
4. TEST Go back to the "File Editor" tab and delete one of the trailing semicolons. Then check the build-log= for a failed compile. You should see a message like "javac stderr: 1 error".
5. TEST Go back to the "File Editor" tab one more time and replace the semicolon. Then check for a successful compile.

Resolve then compile when ivy.xml changes

1. In the same application, open the ivy.xml file and remove all of the <dependency> elements.
2. TEST Check the build-log for a failed compile.
3. TEST Replace the elements and check for a successful compile.

Resolve then compile when dependencies change

1. In the same application, open the "Dependencies" tab and remove all of the items in the list.
2. TEST Check the build-log for a failed compile.
3. Go back to "Dependencies" and add the zero.core dependency.
4. TEST Check the build-log for a successful compile.

Debugger

1. Follow the instructions above for "Copy from Repository (Create Employee Demo)"
2. Click on the debug tab and open app/resources/employees.groovy using the navigator on the left side
3. Set a breakpoint on the line that assigns a value to result in the onList method

   def onList() {
   
   	try {
   		// Get configured DataManager for data access
   		def data = zero.data.groovy.Manager.create('employee_db')
   
   		// Retrieve employee records via Data Zero
   		// *SET A BREAKPOINT ON THE NEXT LINE*
   		def result = data.queryArray('SELECT * FROM employees')
   		
   		request.view = 'JSON'
   		request.json.output = result
   		
   		render()		
   	} catch (Exception e){
   		if (e.getCause() instanceof java.sql.SQLException) {
   			request.status = HttpURLConnection.HTTP_INTERNAL_ERROR
   			request.error.message = "The db may not have been initialized."
   			request.view = "error"
   			render()
   		}
   	}
   }
   

4. TEST Check that the breakpoint icon appear next to the line
5. TEST Click "Breakpoints" tab and verify that the new breakpoint is listed with the correct line number, e.g. "employees [line:24]"
6. Uncheck the checkbox next to the new breakpoint in the Brekapoints tab to disable it and
7. TEST verify that the icon next to the breakpoint in the code viewer has changed to indicate that it is disabled
8. Re-enable the breakpoint by rechecking the checkbox
9. Go to employees.demo client and click "List Employees" to fire a request to the onList() method
10. Go back to debugger and click "Refresh" button
11. TEST Verify that all of the local variables are visible in the "Variables" tab. At the time of this writing, those were: data, this. Also verify that you can expand each of them and that any values or types are correct as far as you know
12. TEST Verify that the current line is highlighted (24) with a yellow arrow cursor to the left and the line highlighted in a pale blue.
13. TEST Verify that the threads view in the bottom right has one thread in SUSPENDED state. Expand the suspended thread and verify that hte top stack frame is the onList() method line 24.
14. Click the "Step Over" button
15. TEST Verify that the "result" variable was added to the Variables tab
16. TEST Verify that the highlighted line changed from 24 to 26 and the yellow arrow cursor moved as well
17. TEST Verify that the top stack frame in the suspended thread now shows line employees.onList(26)
18. Click "Resume" button
19. TEST Verify that all buttons are grayed out except "Refresh"
20. TEST Verify that there are no SUSPENDED threads in the threads view
21. TEST Verify that the variables view no longer shows any variables

iWidget Create and Test

Please follow these detailed steps.

Visual page editor

Please follow these detailed steps.

Visual flow editor

Please follow these detailed steps.

ZRM model editor

Please follow these detailed steps.

ZRM form editor

Please follow these detailed steps.