You are on page 1of 36

Automated Testing

Copyright
Copyright © 2002 IPNetFusion Inc.
3400 Waterview Parkway
Richardson, TX 75080, USA
All rights reserved
Printed in the United States of America

Warranty
Information in this guide is subject to change without notice.
Companies, names, and data used in examples herein are
fictitious unless otherwise noted. No part of this guide may be
reproduced or transmitted in any form by means electronic or
mechanical, for any purpose, without express written
permission of IPNetFusion Inc.
Contents
AUTOMATED TESTING..............................................................................................1
INTRODUCTION TO THE TEST SUITE RUNNER................................................2
Test Profile Creation..................................................................................................3
Test Profile Execution................................................................................................5
Functions Of Log, Log as Text, Execution Level And Display Level......................5
File Menu...................................................................................................................6
Edit menu...................................................................................................................7
View Menu..............................................................................................................10
Scheduler.................................................................................................................14
INTRODUCTION TO REPORTER...........................................................................16
Use Case For Reporter.............................................................................................17
RUN REPORTER…………………………………………………………………….26

LOGGER.......................................................................................................................22
Edit...........................................................................................................................24
View.........................................................................................................................26

iii
Automated Testing
A key feature of EAST is the capability to run automated
testing. In order to run automated tests, a system not only needs
the tools to build messages and test protocols, but also should
be able to manage several discrete aspects of a test. Managing
discrete aspects simultaneously can be quite complicated,
considering that each action must be executed, confirmed and
logged for verification.
Some capabilities of EAST for supporting automation are
mentioned below:
 Call Processing Test Automation
 Network Management
 Graphical Editors
 Alarm Monitoring
 Fault Creation
 Test Runner/Scheduler
 Resource Management
 Logger
 Reporting
 Test Management

Automated Testing 1
Introduction to the Test Suite Runner
The test suite runner is used to execute the test suites. Using
the runner, the user can schedule the test suites to run within a
specified time interval. It can be invoked directly through the
desktop from the runner list. The Event server and Schedule
server should be active on the desktop to invoke the TS runner.

The test suite runner is shown in the following figure: -

The functions of the test suite runner are divided into three
categories: -
 Test profile creation

2 EAST
 Test profile execution
 Scheduling the test suites

Test Profile Creation


Need of Test Profile
A profile keeps the current settings of the runner window in a
file format. The extension name of the profile is “. profile”. It is
saved in the {ROOT_DIR}\\data\\config\\profile folder. The
runner loads the profile and runs the test cases, which are saved
within it. If no profile is created then the “default profile” is
loaded during execution.
Test Profile Panel
When user clicks the test profile creation tab pane, the
following GUI appears: -

Test Profile Name


In the Test profile name text field, we enter the profile name.

Automated Testing 3
Test Profile Creator
In the Test profile creator text field, we can enter the name of
the user who has created the profile.
Description
In this text-field user can add any description about the test
cases that is to be executed or any other text that the user feels
would be suitable.
Test Cases Panel
In the test cases panel a test case list is displayed. On any test
suite name we can write click and a pop up menu will appear
showing three options i.e., View Test Suite, Arguments and
Delete.

View Test Suite


Using this option the test suite can be viewed from the runner.
A test suite editor will be opened to display that test suite.
Delete

4 EAST
Clicking this option the test case can be deleted from the test
case list. When the delete option is clicked, a confirmation
dialog comes as shown below: -

Test Profile Execution


In test profile execution panel the test suite is executed. In this
panel, there are facilities for display settings, setting filters for
TIOs, to view the logs, and to view the event trace.
View Types
Different view types in the runner are Text view, Event Trace,
TIO view, Graph view and HotPoint.
For more information on view types, see details

Filter Settings
The filter settings panel helps the user to view the logs as
desired.
For more information on filter settings, see details

Functions of Log, Log as Text, Execution


Level and Display Level
For more information on Log and Log as Text, see details.

Functions of the Different Menus

File Menu
Automated Testing 5
Load Test Suite (Ctrl+Shift+L)
This option opens a dialog box displaying all the scripts in the
{ROOT_DIR}\\data\\ts\\script folder. The desired script can be
loaded for execution.
Load Profile (Ctrl+L)
This option opens a dialog box displaying all the existing
profiles in the {ROOT_DIR}\\data\\config\\profile folder.
Save Profile (Ctrl+S)
This option allows the user to save the profile.
Save Profile As (Ctrl+Shift+S)
This option helps the user to save a profile in another name.
Run (Ctrl+R)
This option is used to execute the loaded script.
Close (Ctrl+C)
This option allows user to close the currently running
application.
Quit (Ctrl+Q)
This option allows user to quit from the runner.

Edit menu

6 EAST
Testbed (Ctrl+T)
It provides facility to enter different test bed names for sending
and receiving messages.
If in the desktop.dos the entry is ‘UseTestbed=no’, then the
originating and the terminating graph will run successfully with
same test bed name.
If in the desktop.dos the entry is ‘UseTestbed=yes’, then the
originating and the terminating graph will run successfully
having different test bed names. If they have the same Testbed
name, the test cases will not be executed successfully.
Test Environment (Ctrl+Shift+E)
It allows user to change the Default entry of Test Environment.

After entering the name in the given text area when the user
clicks on the “Apply” and “Okay” button, this name is
reflected in the Runner.

Automated Testing 7
Search (Ctrl+F)
Search allows the user to search for a string in the log window.

Find Next (F3)


Find next takes the user to the next match from the most recent
Search.
Properties (Ctrl+P)
The property options displays a dialog box in which the
properties of the logs can be set.

8 EAST
Runtime (Ctrl+N)
The Runtime Dialog option allows the user to know how much
time is required to execute that Test Suite.
Suppose if user enters 10 Seconds, then the TS is executed for
10 sec, if it is not executed with in this time then TS is aborted.

View Menu

Automated Testing 9
The View menu has five options: Debug, Dump Object
Counter, Messages, Status, and Reporter.
Debug (Ctrl+D)
The Debug Option shows the log level status to the user. If
users enter ll 6 and clicks the Debug button, then it sets the log
level as set log level 6 on the Debug Viewer window. Now if
we run the TS, then it shows all the details in the Description
column.
Clear tab will then clear all the data of the Debug Viewer
window.
Clicking on the Log To File button will save the details of the
Debug viewer window in a Text format on the path :
Data\Logs\RunnerDebug.

Dump Object Counter (Ctrl+M)


The Dump Object Counter Option displays the information of

10 EAST
objects being used. If user selects the Show All Objects then it
displays all the objects and the status of each object..

Messages (Ctrl+Shift+M)
It stores the status shown in Status bar of the TC Runner
serially.
Status (Ctrl+U)
The Status window of the Test Suite runner displays the status
of the selected test suite after execution. It includes information
about the Success and Failure of the test cases. See details.
Example: The user tries to execute a test suite, which calls
three TC’s through the TC List TIOs. The return types of the
two TC’s are success and one TC is Failure. The Status window
will show the Status as shown below.

Automated Testing 11
Favorite

The Profiles that we want to use regularly can be added into


favorites by clicking the “Add to” option.
The create folder prompts for a folder name to create a
submenu inside the main favorites menu.

The “Add to” option comes automatically inside every folder


as shown in the following figure.

12 EAST
Help Menu (Alt+H)

Help Topics
By clicking the Help Topics it displays the detailed description
about the selected TIO or Editor.

About
When user clicks on the ‘About’ button, it displays the EAST
version and JDK version that we are using currently in our tool.

Automated Testing 13
Scheduler
The user is able to schedule the test suite in a regression
environment to execute at a later time. To invoke the scheduler,
the user has to select scheduler panel in the runner. In the
scheduler window the user can select test suites and input the
number of times to execute the test suites.

14 EAST
Once the “More” check box is selected the following dialog
will appear.

Automated Testing 15
The user can schedule the test suites, according to the choices
shown in the picture above. The user can enter the maximum
execution time for a test suite or the pool of test suites in terms
of seconds, minutes, or hours.
An option for the generation of the Log File is included. If the
Log file is scheduled, then the relevant log files are generated,
otherwise no log files will be generated.
The Schedule frequency option allows the user to execute the
test suites once, daily, weekly, or monthly.
The “Exit runner after execution” option has two choices,
yes and no, for exiting the runner after execution of the Test
Suite. Test Environment sets the environment of the Test Suite.

16 EAST
Introduction to Reporter
The reporter is one of several automation features that allows
users gather detailed information of test cases and test suites
that were executed from the Desktop Reporter, Scheduler, or by
executing a load pool from the MGCP Load Runner. It keeps a
detailed report of some of the test suites statistics, such as the
time of execution, number of TCs used, whether or not the
graph was completed, etc. The Reporter is invoked by clicking
the “Reporter” button of the Desktop. The window of the
Reporter is called “Test Reporter”.

Test Reporter
The Test Reporter displays the TS Name, User, Test Suite, and
Status.
For the individual TC’s, the TC Name, Status, Start Time, End
Time, Test Duration and Comment are displayed.
Test Reporter Window has two panels; the left panel reflects
Test suites whereas the right panel shows the corresponding
TC’s of the selected Test Suite.

Left Portion of The Test Reporter Window:

Automated Testing 17
 Start: Date and time of execution of the test suite.
 User: Displays the Login name of the user who ran the
Test Suite.
 Test Suite: The name of the Test Suite executed. The
name of the load pool/Choice/Test suite is displayed n
the case of a load pool,.
 Status: Shows whether the TS ran successfully
(Complete) or not (Incomplete).
Right Portion of the Test Reporter Window:
 Test Case: Name of the test cases used in the selected
Test suite.
 Status: The status of the test case: Success, Failure, or
in progress.
 Duration: Total execution time of the test case.
 Comment: The comments of the TIO (Set in the End
TIO of the test case)

Use Case for Reporter


 Select "Reporter" tool from the Desktop. The choice lists
in the window helps filtering the files. The left choice list
has only one option (i.e. within). And the right choice list
has four options (i.e. minutes, hours, days, and week).
Changing the choices in the choice list will filter the files.
 Enter the appropriate value in the text field. By default, the
value appearing in this field is 60 minutes. Click the
“Filter” button, so that the filtered files will appear in the
Reporter as shown in the figure below. (here all files ran by
administrator within the last 60 minutes)

18 EAST
 To view the log information of the executed test case,
select a Test suite file from the left list and then select the
“View Log” button in the Reporter. If the log file exists, it
will be displayed in the Log Viewer.

Automated Testing 19
 If no log file exists for the selected Test Suite then it shows
the “Log file not found” message on the Status Bar of the
Test Reporter.
 Click the “Detail” option to view the details for a selected
test suite result. The following window appears:

20 EAST
 Click the “Print” button to print the details of the test suite
result.
 Select a TS table from the left panel window. Once the TS
is selected, the View choice list will be activated. There are
four choices to view the status of the TS: All, Success,
Failure, In Progress, and Incomplete. The All option is the
default state.

Automated Testing 21
 Click on the File: Preview. A dialog window will appear
that shows the details of the selected TSs, as well as the
corresponding test cases.
 Let the preview window stay as it is. Now select File:
Save. A save file dialog will appear on the screen. Select
the directory and give the file name in the specified space
and click “Save” to save the test data of the selected TS
(and the corresponding TC’s) in a text file (the name
followed by .txt) in the specified directory.

22 EAST
 Click the “Quit” button to exit from the Reporter window.

Automated Testing 23
Run Reporter
It is one of the important features of EAST that displays the
Event trace in HTML format and also the offline logs. It can be
invoked from Desktop-->Admin-->Reporter as below

On selecting Reporter option from Admin button the Reporter


window appears as below

24 EAST
It contains three menus as File, tools and Help. File menu
contains one option as “Refresh” which is used for refreshing
the window.

Tools menu contains three options as Logger, Event Trace and


Show unsuccessful TCs.
Logger option is used to display the offline logs of selected
test case.
Event Trace option is used to display the event trace of selected
test case in HTML format.
The Show unsuccessful TCs option is used to display the
details of unsuccessful TCs called in a Test suite.

On selecting the Event Trace option the event trace of selected


TC is displayed as below.

Automated Testing 25
The Help menu contains as the following options: Help Topics
and About

To view the event trace the user has to select the


“SaveAsHTML” option from filter setting panel of the runner
window. And for viewing logs the user has to keep the log
button “ON”.

26 EAST
Automated Testing 27
Logger
When a test case is executing in regression mode, a log
showing details of each and every TIO executed can be created.
The details include the name of the TIO, time of execution,
return result from the TIO, and other details specific to that
TIO. These log details can be stored in a file so that they can be
used for further use. The log file describes the execution path
of the test logic from the start to the end. In these files the user
can see the resources acquired, timers set, timer expiration,
user input text, etc.
The Logger window as shown below consists of different
menus and the log file selection window.

The menu bar of the logger window appears a shown below:

28 EAST
File

Open (Ctrl+O)
Opens the Log file.
Procedures:
 Select File:Open and the window shown below will
appear.
 Select a Logs folder showing time stamp from the
window and then click the Ok button.

Automated Testing 29
 The window shown above contains all the log files
having time stamp that can be viewed through the
logger.
 It contains the filenames of the test cases that were
executed with its extension coded as the date and time
stamp.
 Select a file name and then click the Open button to
open the log file.
Save as
This command saves the log files in text format.
Close
This command closes the currently opened log file.
Quit
This command quits the logger window.
Edit
This menu has two options: “Search” and “Properties”.

30 EAST
Search
The search option is used for searching the log steps from the
logger window.

Automated Testing 31
Properties
The properties option takes the user to the properties dialog,
which shows the page with all the properties.

32 EAST
View
This menu has one option: “Status”, “Debug”, “Dump object
Counter” and “Messages”.

Event Trace
For event trace, see details.
Filter Settings
Filter gives a brief description of the log files displayed. Here a
filter can be set on the log messages that are to be displayed.
For more information, see details.

Go To Main

Automated Testing 33

You might also like