1.1 Installing the TM Development IDE and Adding New Transaction Tests

Transcription

1 The General Idea Behind Monitis Application and Transaction Monitoring Service. The Monitis TM Recorder allows the user to record interactions with a web-based application step-by-step and to continuously check each step for faulty areas. To precisely pinpoint the sought interaction, the user is allowed to playback the recording several times and to edit any steps that are in a need of a revision. After the recorded script is polished and finalized to the user s taste, it is uploaded to the Monitis server and installed on the global monitoring network to playback through the desired transaction at specified intervals. Upon creating the monitor, the user can choose playback intervals of an hour, half an hour, fifteen minutes, or even five minutes. When the test results become available, the user may view the gathered data on either a tabular or a graphical display. The graphical display will show the monitoring results per each check, while the tabular display will show a list of the gathered data. Either of the data display will clearly indicate if any of the transactions have failed. To gather more information about the failed test and to find out exactly what went wrong, the user may double click on the failed test and any critical information will be displayed on a pop-up window. Different screenshots will also be available to scrutinize the issue in more detail. 1 TM Service Features The usage of TM module can be divided into following steps. 1. Creating and executing transaction tests. 2. Adding reports. 3. Adding rules. 4. Sending notifications 1.1 Installing the TM Development IDE and Adding New Transaction Tests The TM service is designed according to Monitis development conventions. Therefore, TM modules can be created, edited, deleted, and displayed just like any other modules. Privileges of adding TM modules are granted according to Monitis account s plan. Consequently, in order to add a transaction test, the client has to be logged in with the appropriate privileges and has to install TM Recorder s FF extension.

2 Adding a TM test is done by selecting the Transactions item from My Monitors menu (See Fig. 1-a). This item will not be included in the list if client does not have the privileges of adding TM module. By clicking on the link inside the prompted window (See Fig. 1-b), the user will be guided through the installation process of Monitis Transaction Recorder extension for Firefox browser (See Fig. 1-c). Pressing the Install Now button will start the extension installer process and after clicking on the Restart Firefox button (See Fig. 1-d), the Monitis Transaction Recorder will become enabled. a) b) c)

3 d) a) Transactions menu item. b) Add Transaction dialog window. c) Extension Installation Window d) Completed Installation Window Fig. 1 If the TM recorder installation has been successfully completed, Tools -> Monitis Transaction Recorder item should be seen in the menu. If this is not the case, check if TM Recorder icon is visible on the lower right-hand corner of the Firefox task bar (See Fig. 2-a). After opening the Monitis Transaction Recorder,using either the menu or the icon from the task bar, the recorder will display a Login tab (See Fig. 2-b), where the user can input his or her Monitis credentials. If the user successfully authenticates, the scripts tab will be opened, listing the client s existing transaction tests. If no transaction tests have been added, this list should be empty. (See Fig. 2-c). To create new tests and record transaction steps the commands tab should be opened with empty Table and the user should be made sure that the recording mode is enabled(see the circled icon in Fig. 2-c). There are three columns under this Table - Command, Target and Value. This Table stores essential information about each step. For any element present on the browser, recorder maps its action with three values: command, target, and value. For example, if a client wants to type a username in the user name text box, the recorder would translate it as

4 command=type, Target=username text box and value=your username For commands related to asserts, a certain value can be specified to compare to another value. For example: command=asserttext,target=label and Value=somethingtocompare. In this case, the recorder will compare the value of the target with the specified value in subsequent execution. The recorder gives the client enough functionality in terms of identifying the target. For instance, the client can locate or identify the target using DOM, ID, Name, XPath etc. Utilizing this resources provided by Monitis, the client can easily create automation frameworks. While working with TM Recorder, the client might find it useful to try Firefox extensions like DOM Inspector or XPath Viewer to get information about the XPath or DOM information of the GUI element under test. Here are the steps required for recording transaction steps: Open Firefox Open the site where the steps should be recorded i.e. (This URL should also be written in the Base URL field at the top of the IDE) Record some steps and make sure that the steps can be seen on the TM Recorder. During the recording phase, the client may right click on any element to view all the available selenium commands. The client can also edit an existing command by selecting the command and editing the displayed information. By choosing the appropriate option after right clicking, the client may also insert/delete commands Client can choose appropriate run option - i.e. walk, run, or test runner and review results. The Monitis Transaction Recorder will record all the steps and will provide additional functions for several checks, i.e. verifytextpresent function (see the last step of recorded test Fig. 3-a), which will check in the content of search result, are there results which contain the Monitis word or not.

5 a) b)

6 c) a) Monitis Transaction Recorder menu item and icon on FF. b) Monitis Transaction Recorder s Login tab. c) Monitis Transaction Recorder s Scripts tab. Fig.2 By clicking on File -> Save As item from the TM development IDE menu, the user will be prompted to fill out the following fields.(see Fig. 3-b). Test Name (should be unique within the client s already existing tests) Tag Name (an optional field) Client should click on Save As button to save the newly recorded test into Monitis system and wait while the dialog box closes automatically. The client may view the Scripts tab to ensure that the newly saved test with the set TestName has been successfully added. (see Fig. 3-c)

7 a) b)

8 c) a) Recorded steps b) Save As dialog window c) Tests List in Scripts tab Fig.3 To edit the test flow, the client should open the Monitis Transaction Recorder and click on appropriate test from the list of tests on the Scripts tab. In the Commands tab, the client should see each step of the corresponding test. To change any of the steps, the user may click on the appropriate step and modify the Command, Target, Value fields associated with the step. After the changes have been made, the user should go to the menu and click on File -> Save item and then click on Save/Update button in the opened dialog window (see Fig. 4).

9 Fig.4 Test s Update Dialog Window 1.2 Viewing Transaction Monitors From the Dashboard To see the results of the added test on Monitis dashboard, the client should go to the Monitis Web Site application and click on My Monitors -> Transactions menu item, and the the user should select the test and click add (See Fig. 5-a). The opened view shows the execution time of the appropriate test per specified interval. Suggested two views of data display are table view and line chart display. The red point inside the line chart shows if any execution has failed for a given time (See Fig. 5-b). By clicking on red points on the line chart, the user may view the list of steps with the corresponding execution times nicely displayed on a bar graph (See Fig. 5-c). The red bar on the graph indicates failed step. To see the error, detailed net diagnostic, and the screenshot for the failed step, click on the red bar.

10 a) b) c) a) Add Transaction dialog window b) Line chart view c) Bar chart view of transaction steps Fig. 5

11 To edit the name or the tag of test, the client should go to edit window by clicking on the edit icon and change the corresponding fields, and then click Apply (See Fig. 6). Fig. 6 Edit view 1.3 Adding Rules for Notifications After clicking on Notifications Rules (See Fig. 7-a), a new dialog window will appear (See Fig. 7-b) allowing the user to set or modify rules for receiving notifications within desired timeframe and conditions. To add a rule for a certain transaction test, the client should select the suggested options and click on the Add Rule button and then press Done. The Notification Period field, having three options Always, Everyday, and Specified Days Only, defines the timeframe within which the failure or recovery alerts should be sent to the user. The number of subsequent NOKs field defines the number of failing results after which a problem alert should be sent. The client should select the Contact group from which he/she wants to choose contact account for appropriate notification rules to be set. To set the rules for all contact groups or for all contacts, the client should select the All value. The use may edit or remove the set rules at any time with much ease.

12 a) Fig. 7 a) Notification Rule Button b) Notification Rule s dialog window 1.4 Adding Reports The client may choose to generate Yearly, Monthly, Weakly, or Daily Transaction reports from existing Transaction monitors. To generate reports, the client should click on the New Report -> Transaction item and in the opened dialog window, should select the report interval, view and also should define report type: tag or test, select appropriate name and define SLA (Service Level Agreement) for showing compliance on data view.

13 Various intervals are suggested to user to choose: yearly monthly, yearly weekly, monthly daily, weekly daily and daily hourly. The client may utilize any of the before mentioned intervals for already created tests. Two types of SLAs are suggested Success rate and Duration related (See Fig. 8-a). Giving a name to the report and pressing on the add button will save the module on the workspace. If the client closes the report from the workspace, the user may reopen the report by going into My Reports -> Transactions menu. By selecting Transaction Report option from the drop down menu, the client should see a list of added reports. There are three views for displaying the data: Table view shows the Success Rate for appropriate intervals and the SR Compliant for that interval (See Fig. 8-b). Line chart each point shows the Success Rate for appropriate interval and the red line shows the SLA (See Fig. 8-c). Bar chart each bar shows the Success Rate while the red line shows the SLA compliance (See Fig. 8-d). If client does not have a report displayed on the current page or the user has closed the opened reports, then the client should move/open report module into the current page, and then press on the Edit icon. On the opened window, the client may modify the report name and set a new SLA value. When the appropriate changes are made and the user is satisfied, the client should press on the Apply button to save the modifications (See Fig. 8-e).

14 a) b) c) d)

15 e) Fig. 8 a) Add Report dialog window b) Table view c) Line chart view d) Bar chart view e) Edit view