[ 
https://issues.apache.org/jira/browse/EDGENT-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15677169#comment-15677169
 ] 

Susan L. Cline commented on EDGENT-305:
---------------------------------------

Okay.   Since I don't want to hold up the release, let me write down what I 
did, and I can add it to the Testing folder later:

Using the ConsoleWaterDetector sample that comes with Edgent:

Verified the console started on the port indicated in system.out
Verified these controls:

The state image popup up on hover / closed on mouse out
The view by: drop down worked properly with all options - static flow, tuple 
count, oplet kind
Refresh interval had a minimum value of 3, even if the user enters 0 or some 
number less than 3. If a number greater than 20 is entered, that is disallowed 
as well.
Pause / resume graph work properly

Show tags checked allows 'Show all tags' to be checked, or when 'Show all tags' 
is unchecked, the 'Select individual tags' is enabled.
Show tags unchecked disables both the show all tags and the select individual 
tags controls

When show tags is checked, the legend 'Stream tags' is added to the page 

when Show all tags is checked, all stream tags are shown in the graph
When 'Select individual tags is checked' individual - one or more can be 
selected from the popup dialog and works correctly.

View by Tuple count works and creates a 'Tuple count' legend when selected
View by Tuple count works with Show tags selected or not

View by Oplet kind works and creates an Oplet kind legend
View by Oplet kind works with Show tags selected or not

View by Static flow creates uniform streams (in size) between the oplets
View by static flow shows these values when hovering over an oplet: Name, oplet 
kind, tuple count (which does refresh), source streams, target streams, and 
includes tags.
Hovering over a counter op or stream scope only shows oplet name and oplet kind.
Hovering over a stream shows source oplet name and oplet kind and target oplet 
name and oplet kind.

View by Tuple count changes the color of the oplets according to tuple flow 
count in the graph and leaves the streams width / coloring unchanged unlesss 
the 'Show tags' control is selected and there are stream tags present.

View by Oplet kind changes the oplet colors according to the legend and leaves 
the size of the oplets unchanged unless multiple oplets are feed into a single 
oplet.  If so, the target oplet accepting multiple streams is increased in size.

View all oplet properties, when clicked, opens a new window:

The table that appears in the new window contains the following columns:
Name Oplet kind, Tuple count (in and and out), Source streams, Target Streams.
The source streams and target streams columns contain values of tuple counts 
and tags if present.

This window is supposed to refresh the values, but it appears there is a bug 
and it is not refreshing.
Clicking the pause button is supposed to stop the refresh.

Metrics section
****************

If metrics are present there should be Metrics drop down.  If counter oplets 
are used, the words: 'Count, oplets:" should appear, listing the names of the 
oplets that are counter oplets.
 The chart type should default to 'Bar chart'.
The chart should have a y-axis label of count if the Count metric is the 
selected metric and the x-axis should say 'Oplets'.
Hovering over one of the bars should display a 'Name' value and a  'Count' 
value.

If metric rates are present, the rate should appear in the Metrics drop down 
too.  For example FifteenMinuteRate and the chart type should be 'Bar chart'.  
The y-axis label should correspond to the value in the drop down.

If more than one oplet is listed in the metric drop down for any of the rate or 
count oplets, the line chart type is disabled.  If only one oplet is present, 
then the line chart option is enabled and shows a running average of the value 
for that oplet.

Hovering over the 'Show metrics in table' displays a popup with 'Name' and 
'value' categorized by either 'Count' or 'Rate type'.  For instance, 

Counter oplet values
Operator name   Counter value
100     1670
101     1879
102     998
37      1043
...
Rate meter oplet values
Operator name   Rate type       Rate value
37      FifteenMinute   0.3585
37      FiveMinute      0.3611
37      Mean    0.3665
37      OneMinute       0.3201
49      FifteenMinute   0.3753
49      FiveMinute      0.4032
49      Mean    0.3914
49      OneMinute       0.3816





> Test the Edgent Console
> -----------------------
>
>                 Key: EDGENT-305
>                 URL: https://issues.apache.org/jira/browse/EDGENT-305
>             Project: Edgent
>          Issue Type: Sub-task
>            Reporter: Dale LaBossiere
>            Assignee: Susan L. Cline
>
> (manual) Testing of the console seems to warrant a separate item.  
> Please update the RM Guide with info for what should be tested, on what 
> platforms, etc



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to