Manual tests for Visual Flow Editor
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
BEFORE YOU START TESTING...
Refer to the DevToolsIdeTests and complete:
- Install and run the App Builder
- Create the new application named FlowTest
- Open the FlowTest
Create simple feed flow
- Click New File and select Flow in /public
- Type test.flow after /public/ and click Create
- TEST verify you get a "Do you want to enable the flow component?" prompt, and click "Add".
- TEST verify the path (including filename) is displayed in the right side of the editor toolbar.
- Click the "Dependencies" tab
- TEST verify the ivy.xml now contains zero.assemble.flow.
- Back to "File Editor" tab.Drag a feed activity from the palette and drop on to canvas.
- TEST verify the feed activity is created successfully.
- Drag and drop feed,aggregateFeeds,sortFeed,replyGET to create a flow as below.
- TEST verify the flow diagram is created successfully.
- Move the mouse to "feed_0" and click the "feed_0" text.Change the name to "YahooNews".
- TEST verify the name is changed successfully.
- Click the Property icon on the right top of the figure.Set the 'url' attribute to http://rss.news.yahoo.com/rss/topstories. Click "OK".
- Change the "feed_1" to "YahooSports" and set the 'url' attribute to http://rss.news.yahoo.com/rss/sports as above step.Click "OK".
- Open the "sortFeed" activity's properties dialog.Set 'sortBy' attribute to 'atom:title'.Click "OK" to close properties dialog.
- Click the "Start" to start the application,point your browser to http://localhost:8080/test.flow.
- TEST verify a feed is shown and feed is ordered by title.
- Back to "File Editor" tab.Click on the "Source" tab at the bottom of the editor.
- TEST verify the flow XML is saved.
- Modify the "title" in aggregateFeeds activity to "My favorite News"
- Save it and Click on the "Design" tab.
- Open the properties dialog of aggregateFeeds.
- TEST verify the "title" attribute is filled with the value "My favorite News".
- TEST Refresh the http://localhost:8080/test.flow, verify the feed title is changed to "My favorite News".
- TEST Undo a few actions; verify changes
- TEST Redo the same number of actions; verify changes and result should match the file before the undo test
- TEST "checkpoint" the file, add another activity, then "restore" the file; Verify the contents match the checkpointed contents
- TEST Rename the file (double click it in the "All Files" view), verify name is updated in toolbar correctly (in Design and Source views)
- TEST Delete the open file (hover over, then click the X icon in the "All Files" view), verify editor is closed when deleted
Create simple collaboration flow
- Click New File and select Zero Resource Model in /app/models
- Type TravelRequest.json after /app/models/ and click Create
- Create the ZRM as following
Or simple copy below model to Model Editor's source.
{
"fields": {
"name": {
"label": "",
"required": false,
"type": "string",
"description": "",
"default_value": "",
"max_length": 50
},
"email": {
"label": "",
"required": true,
"type": "string",
"description": "",
"default_value": "",
"max_length": 50
},
"manager": {
"label": "",
"required": false,
"type": "string",
"description": "",
"default_value": "",
"max_length": 50
},
"purpose": {
"label": "",
"required": false,
"type": "string",
"description": "",
"default_value": "",
"max_length": 50
},
"destination": {
"label": "",
"required": false,
"type": "string",
"description": "",
"default_value": "",
"max_length": 50
},
"departure": {
"label": "",
"required": false,
"type": "date",
"description": "",
"default_value": ""
},
"approve": {
"label": "",
"required": false,
"type": "boolean",
"description": "",
"default_value": ""
}
}
}
- Click New File and select Flow in /public
- Type TravelRequest.flow after /public/ and click Create
- Click the Collaboration in the right palette
- Drag and drop webUI,sendMail activities and connect the link to create the flow as below.
- Rename activities' name to travelRequest, travelApprove, sendApproval, sendRejection as below.
- Double click travelRequest activity to pop up the property dialog.
- Click the Create UI beside the view input box.
- TEST verify the WebUI Editor pop up as below.
.
- Select TravelRequest in "Outgoing Data for travelRequest" section.
- Move mouse over approve row and click
to remove approve row.
- TEST verify the WebUI Editor now like below.
- Click OK to close the WebUI Editor.
- TEST verify the view attribute now is filled with /travelRequest.gt.
- Click OK to close the property dialog.
- Double click travelApprove activity to pop up the property dialog.
- Click the Create UI beside the view input box.
- Select TravelRequest in two selections.
- Remove approve row in Incoming Data for travelApprove section.
- Only keep approve in Outgoing Data for travelApprove section.
- TEST verify the WebUI Editor now like below.
- Click the Edit in approve row and select the ElementType to radio.Then click save to apply the change.
- Click OK to close the WebUI Editor.
- TEST verify the view attribute now is filled with /travelApprove.gt.
- Click Advanced checkbox to show the optional attributes.
- Fill the attribute assignTo as ${travelRequest.manager}
- Fill the attribute title as Please approve the travel request
- Select the input data from drop down box as ${travelRequest}.
- Open sendApproval activity properties dialog and fill the attributes and inputs as below. subject --> Your travel request has been approved address --> ${travelRequest.email} body --> Your travel request has been approved .
- Click OK to close the property dialog.
- Open sendRejection activity properties dialog and fill the attributes and inputs as below. subject --> Your travel request has been rejected address --> ${travelRequest.email} body --> Your travel request has been rejected .
- Click OK to close the property dialog.
- Click link between travelApprove and sendApproval.
.
- Click the property icon and fill the condition with travelApprove.approve.
.
- Click OK to close the property dialog.
- Click link between travelApprove and sendRejection.
- Click the property icon and fill the condition with !travelApprove.approve.
- Click Ok to close the property dialog.
- Open zero.config
- Add follow config to zero.config
/config/connection/defaults/smtp/hostname = "smtp.hursley.ibm.com"
- Click the "Start" to start the application(restart if it's running), point your browser to http://localhost:8080/TravelRequest.flow.
- TEST verify the UI like below.
.
- Fill the form.Make sure fill the email and manager with your email so that you can receive the notification mail.
.
- Check your mail(Actually the mail address filled in manager field in above step).
- TEST verify you get the notification mail.
.
- Click the *Click here to open the web page * link to open the approve page.
- TEST verify the UI like below.
.
- Click yes in approve and click Submit
- Check your mail(Actually the mail address filled in email field).
- TEST verify you get the travel request approved notification mail.
.
Add extension activity
- Open zero.config in the project
- Add follow config to zero.config.
/config/activity/metadata/myActivity = {
"attributes" : [
{"name":"message"},
{"name":"url", "required":false}
],
"inputs" : [
{"name": "body", "occurrence": "0..1"}
]
}
- Swith Tab from File Editor to Explorer
- Upload file
to /public/tooling/icon-activity/myActivity.png. (Note:Need create empty directory /public/tooling/icon-activity before upload. The file name should be "myActivity.png", you may need to rename the image to "myActivity.png" when you save the manual test image to your computer)
- Upload file
to /public/tooling/figure-activity/myActivity.png. (Note:Need create empty directory /public/tooling/figure-activity before upload. The file name should be "myActivity.png", you may need to rename the image to "myActivity.png" when you save the manual test image to your computer)
- Create a new file /public/tooling/categories/myactivities.json
- Input following JSON into it:
{
"name" : "My activities",
"description" : "My activities",
"item" : [
{
"name" : "myActivity",
"type": "myActivity"
}
]
}
- Create a new flow file /public/testextension.flow
- TEST verify a new category 'My activities' is shown in the palette
- TEST verify myActivity is shown in the palette and the icon is the one added in step 4.
- Drag the myActivity to the canvas.
- TEST verify a myActivity is created in the canvas and the figure is the one added in step 5.
- TEST Hover the mouse on warning icon , a tip will be shown up.
- Double click the figure to pop up the property dialog
- TEST verify the attribute and input are shown as below.
- Click the Advanced check box
- TEST verify the optional attribute ‘url’ is shown.
|
| | Attachment | Action | Size | Date | Who | Comment |
| TravelRequestModel.PNG | props, move | 23.1 K | 10 Nov 2008 - 12:07 | liwenb | |
| WebUIEditorStart.PNG | props, move | 9.9 K | 10 Nov 2008 - 12:08 | liwenb | |
| activitySource.jpg | props, move | 99.5 K | 26 Oct 2008 - 10:20 | liwenb | |
| activitySourceModified.jpg | props, move | 69.3 K | 26 Oct 2008 - 10:21 | liwenb | Changed flow source |
| activityUpdate.jpg | props, move | 38.7 K | 10 Sep 2008 - 03:09 | liwenb | activity after source changed |
| addFlowDependency.jpg | props, move | 19.3 K | 31 Jul 2008 - 15:55 | liwenb | Add flow dependency |
| categoryAdded.jpg | props, move | 4.9 K | 28 Oct 2008 - 06:05 | liwenb | Category added |
| changeAttributeInProperty.jpg | props, move | 29.1 K | 31 Jul 2008 - 16:00 | liwenb | property dialog |
| collaborationFlowApprove.PNG | props, move | 16.2 K | 10 Nov 2008 - 11:59 | liwenb | Approve View editing |
| collaborationFlowApproveLink.PNG | props, move | 18.8 K | 10 Nov 2008 - 12:00 | liwenb | Select link to edit |
| collaborationFlowApproveLinkEdit.PNG | props, move | 6.9 K | 10 Nov 2008 - 12:02 | liwenb | Edit link |
| collaborationFlowApproveRadio.PNG | props, move | 19.1 K | 10 Nov 2008 - 12:02 | liwenb | Edit boolean using radio |
| collaborationFlowApproveUI.PNG | props, move | 9.3 K | 10 Nov 2008 - 12:03 | liwenb | Approve UI |
| collaborationFlowApproveView.PNG | props, move | 11.8 K | 10 Nov 2008 - 12:03 | liwenb | |
| collaborationFlowDraft.PNG | props, move | 36.1 K | 10 Nov 2008 - 12:04 | liwenb | |
| collaborationFlowNotifApprove.PNG | props, move | 10.5 K | 10 Nov 2008 - 12:04 | liwenb | |
| collaborationFlowNotifDONE.PNG | props, move | 8.7 K | 10 Nov 2008 - 12:04 | liwenb | |
| collaborationFlowRenamed.PNG | props, move | 18.9 K | 10 Nov 2008 - 12:05 | liwenb | |
| collaborationFlowRequest.PNG | props, move | 15.3 K | 10 Nov 2008 - 12:05 | liwenb | |
| collaborationFlowRequestUI.PNG | props, move | 6.3 K | 10 Nov 2008 - 12:05 | liwenb | |
| collaborationFlowRequestUIFill.PNG | props, move | 7.8 K | 10 Nov 2008 - 12:06 | liwenb | |
| collaborationFlowRequestView.PNG | props, move | 8.7 K | 10 Nov 2008 - 12:06 | liwenb | |
| collaborationFlowSendAppoval.PNG | props, move | 14.1 K | 10 Nov 2008 - 12:24 | liwenb | |
| collaborationFlowSendRejection.PNG | props, move | 13.8 K | 10 Nov 2008 - 12:07 | liwenb | |
| feedChangeName.jpg | props, move | 6.6 K | 10 Sep 2008 - 02:32 | liwenb | Change actiivty's name |
| feedFlow.jpg | props, move | 20.3 K | 10 Sep 2008 - 02:29 | liwenb | Feed flow |
| feedresult.jpg | props, move | 106.1 K | 10 Sep 2008 - 02:50 | liwenb | Flow result |
| flowDependencies.jpg | props, move | 31.0 K | 10 Sep 2008 - 01:51 | liwenb | Dependencies with zero.assemble.flow |
| fullflow.jpg | props, move | 31.0 K | 31 Jul 2008 - 15:59 | liwenb | flow with get and replyget |
| myActivity-figure.png | props, move | 3.0 K | 28 Oct 2008 - 05:59 | liwenb | The figure of myActivity |
| myActivity-icon.png | props, move | 0.2 K | 28 Oct 2008 - 05:52 | liwenb | Custom activity icon |
| myActivityCreated.jpg | props, move | 5.7 K | 28 Oct 2008 - 06:22 | liwenb | myActivity is created |
| myActivityInCategory.jpg | props, move | 3.9 K | 28 Oct 2008 - 06:20 | liwenb | myActivity in custom category |
| myActivityPropertyAdvanced.jpg | props, move | 25.4 K | 28 Oct 2008 - 06:31 | liwenb | property dialog with advanced checked |
| myActivityPropertyUnAdvanced.jpg | props, move | 22.7 K | 28 Oct 2008 - 06:29 | liwenb | Activity property without advaned |
| setFeedAttributeInProperty.jpg | props, move | 18.2 K | 10 Sep 2008 - 02:36 | liwenb | Set activity attribute |
| setFeedAttributeInPropertySecond.jpg | props, move | 19.4 K | 10 Sep 2008 - 02:38 | liwenb | |
| sortProperties.jpg | props, move | 27.6 K | 10 Sep 2008 - 02:42 | liwenb | sortFeed properties |
| uploadMyActivity-icon.jpg | props, move | 17.0 K | 28 Oct 2008 - 05:55 | liwenb | Upload myactivity icon |
| uploadMyActivityFigure.jpg | props, move | 17.6 K | 28 Oct 2008 - 06:00 | liwenb | Upload myactivity figure |
| warningInActivity.jpg | props, move | 8.9 K | 28 Oct 2008 - 06:23 | liwenb | Warning message in myActivity |
| webUIDel.png | props, move | 1.2 K | 10 Nov 2008 - 12:07 | liwenb | |
r13 - 05 Dec 2008 - 06:24:26 - liwenb
|
|
|