Overview

A scenario specifies the mix of different users accessing web application and hence executing different test scripts. Users may be grouped in different groups and have different user characteristics.

  • Scenario is the overall definition of a test.
  • Scenario may have one or more groups.
  • Each group consists of a number of virtual users executing a test script.

Scenario Profile

NetStorm have scenario profiles to keep default configurations specific to a subproject at a common place.

Key Settings in Scenario

There are following key features of Scenario:

  • Schedule Settings: In this section, user can set up the scenarios and can perform following actions on them, such as adding a group, setup scenario schedule options, setup global schedule and setup various phases. The resultant scenario schedule is displayed in the form of a graph in Schedule graph Section.
  • Global Settings: Global settings are those settings which can be set up and applied globally across all groups. These are not group specific.
  • Group Based Settings: This section provides the settings which are Group based. User can add group based settings to their scenarios from here.
  • Monitors Settings: This section is used to apply certain monitor based settings. 
  • Server Mapping: This section provides settings related to server. NetStorm maps the recorded host (name of the host where the script was recorded) to the actual host (which is being tested). This maps one recorded host to one or more actual servers and their locations.
  • Real Browser User: In this section, user can perform Group based real browser settings, such as cache settings, Har settings, as well as Global setting, such as screen size, other browser based settings for real browser user. 
  • SMTP Settings: Simple Mail Transfer Protocol (SMTP) is an Internet standard for electronic mail transmission. User can perform SMTP settings in this section. 
  • Java Settings: This section provides settings related to execution of java type scripts, such as JVM memory size.
  • NetDiagnostics Settings: This section provides settings related to NetDiagnostics. User can perform enable/disable setting of NetDiagnostics from here.
  • Health Monitor Settings: In this section, user can set system health information, such as free memory or disk mode.

Login to NetStorm

Follow the below mentioned steps to login into NetStorm portal:

  1. Enter the following URL (http://hostname/netstorm) and press ENTER. The NetStorm login window is displayed.

1

  1. Enter the Username and Password and click the Login button. The Product UI Home page is displayed.
 NoteThe default username and password is netstorm/netstorm.

NS Home page consists of a left pane and a right pane. Left pane contains menu to view details on test runs, scenarios, monitors, and various other sections. Using these menu, user can access further sections and can perform various operations, such as compare test runs, generate reports, access various features of web dashboard and executive dashboard, and so on. In the right pane, summary of the important aspects is displayed, be it a release version, CPU usage, memory utilization, or alerts generated in the system.

Left Pane

It contains following menus / sub-menus, and menu items:

View

  • Dashboard: This displays the current Dashboard.
  • Test Runs: Shows the test runs window.
  • Scripts: To launch script manager and create a script.
  • Scenarios: To create scenarios.
  • Run Time Progress: This shows the run time progress of the test. This is only available when the test is running currently.
  • Virtual User Trace: This is used for tracing the users for different group(s).
  • Transactions: This displays detailing of all transaction(s) in current test run.
  • Show Vector in Title: To view graph with breadcrumb, such as last 1, 2…5.
  • Events: This shows all event(s) generated in current test run.
  • System Logs: To view system related logs, such as Kubernetes logs, RBU access logs, peripheral device logs, and system events.
  • Logs
    • Test Output: This shows the test output in browser as well as on panel.
    • Debug Trace Log: This displays debug trace logs if Debug feature is enabled in scenario.
    • Pause Resume Log: This is used to view the logs for paused/resumed test schedule (if any).
  • Stats: It shows the TCP connection information and is available if test is running currently.
  • Application Health: To view application health.
  • Application End to End View: To view end to end monitoring approach.
  • Geo Map: To view Geo map.
  • DB Monitoring: This is a powerful feature to measure the performance of each query contributing in a session execution. It provides complete monitoring of MSSQL queries with insights into SQL activity, wait statistics, databases, support services, Temp DB, and high availability. It enables a user to detect such queries, which are consuming more resources as compare to normal ones. Once identified, user can diagnose the issue and perform corrective measures.

Analytics

  • Compare: This feature is used to compare two test runs. User can perform further actions for post compare operation:
    • Disable Compare: To disable the comparison applied and back to original form.
    • Update Compare: To update the inputs provided for comparison.
    • Scenario Difference: This displays scenario difference between current and baseline test run.
    • Script Difference: This displays script difference between current and baseline test run.
    • Server Signature Difference: This displays server signature used in current test.
  • Derived Metrics: This feature is used to create a derived graph from two or more graphs.

Favorites: Favorite allows a user to save current view of Real Time Graphs (RTG). User can create a new profile by saving current view of RTG UI as a profile. If user wants to see current view of graphs next time in Web Dashboard, then user needs to add graphs in favorite. When user loads saved favorite, then all graphs of favorite are displayed in Web dashboard’s graph panel.

Alerts

  • Alert Maintenance Window: This window provides alert maintenance configuration to disable generation of alerts at the time of maintenance or server goes down.
  • Alert Settings: This is used to enable/disable alert configuration, such as alert mail, capacity alert, and thread dump.
  • Alert Policy: This is used to create policy for specified condition and rules.
  • Alert Actions: This is used to create actions, such as alert mail, thread dump, and TCP dump.
  • Rules: This is used to activate/deactivate/add/delete/update rules.
  • Active Alerts: This is used to see generated alerts, such as capacity alerts.
  • Alert History: This is used to see the alerts generated in the past.
  • Active Alert Graphs: This is used to generate graphs for active alerts.
  • Alert Stats Report: This is used to generate stats report for alerts.
  • Alert Action History: It contains details of action taken by alerts, such as SNMP Trap Sent / Email Sent / Cisco Spark Chat sent and so on.

Configuration

  • Monitors: To configure the monitors.
  • Show Monitors: To view the configured monitors.
  • Update Monitors: To update monitors.
  • Topology: To configure topology.
  • Batch Jobs: To configure batch group and batch jobs.
  • Tier Group: To configure tier group list.
  • Agent Config: For ND agent configuration.
  • Configuration Settings: For various settings, such as dashboard settings, multi-node configuration, show vector in title, and graph tree.
  • Color Management: It is used to define the color of the graphs.
  • Manage Catalogue: It provides a common platform for the selection of graphs and storing them as a catalogue.

Reports: Reports menu is used to create various types of reports, such as stat report, compare/trend report, hierarchical report, and so on. These reports are generated using templates and have other advanced options to include all or selected metrics. The reporting format may be selected as Word, HTML or Excel. It includes tabular data with or without graphical illustration.

Actions

  • Thread Dump: To take thread dump, analyse thread dump, and schedule thread dump.
  • Heap Dump: A heap dump is a dump of the state of the Java heap memory. This is useful for analysing the use of memory i.e.an application is making at some point in time so handy in diagnosing some memory issues, and if done at intervals handy in diagnosing memory leaks. User can take heap dump from here.
  • Process Dump: To take process dump.
  • TCP Dump: This option is used to take the TCP dump.
  • Mission Control: It is a property through which user can get thread JVM information for JRocket. This includes two features – Memory Analyzer and Flight Recorder.
  • Java Flight Recording: To view all java flight recordings.
  • Sync points: Sync points means ‘meeting points’. A Sync point creates intense user load on the server at a time to measure server performance under load.
  • Launch SSH Console: Logged-in users can access a sandbox view of the Linux terminal from the NetStorm, NetCloud, and NetOcean browser. Select Actions > Launch SSH Console to open a terminal window to access your workspace where your test assets are present. You can update the test assets, like scripts, using the VI editor and then commit your changes to your GIT repository.
  • Run command: This is used to run command on server.
  • Download File: To download a file from the system.
  • Import data from Access Log file: This imports data from access log file.
  • Update:
    • Update User/Session Rate: This updates user/session rate (Online mode only).
    • Update Data File: To update data file, it is supported in online mode only.
    • Update Running Scenario: To update running scenario (in online mode only).
    • Update Session: Enables you to increase/decrease the number of sessions (based on availability)
  • Manage Vusers: To manage Vusers, such as start, stop, pause, and so on.

Admin

  • Projects: Displays the Project Administration window to add, delete, rename a project / sub-project.
  • LDAP Server Settings: To configure LDAP Server settings.
  • Servers: DisplaysServer Administration windowto configure a server.
  • Settings: To configure module tab settings.
  • Manage Controllers: To manage controller with details, such as appliance name, controller name, controller URL, and Service End point IP.
  • GIT Settings: To perform GIT Remote Server settings.
  • Retention Policy: To configure the data retention / data backup policy (NDE Purge)
  • Access Control: To perform identification, authentication and accountability of entities through login credentials including passwords.
  • Agent Info: To view machine agent status and application agent status.
  • NetHavoc: A feature to implement resilience testing.

Advanced

  • Automation: This constitutes Test Suite, Test case, and Test Reports.
    • Test Suite: Test Suite is the NetStorm entity to control the execution of tests together with the comparison of actual outcome to predicted outcome (SLA).
    • Test Case: Test Case provides an automated way to run a Test scenario.
    • Test Reports: HTML report generated after test execution.
  • Script Conversion: A user can convert a JMeter script, Load runner script, and HAR script into Cavisson Script using the script convertor provided by Cavisson. Post this, user can view the converted script in NetStorm Script manager and can view the Scenario via NetStorm’s Scenario UI. This section is covered in NetStorm Script Manager User manual..
  • Postgres Stats: This displays overall connection stats that includes Max connections, reserved connections, used connections, and available connections. Apart from this, a user can view detailed connection stats based on database and application.

Right Pane

This sections provides a summary of the most details related to release, memory, and CPU utilization. It contains following sections:

Release DetailsThis section provides release details of product, such as release version and build number, the time when the release is installed on the server. It also provides a tabular view where user can see the release details, such as installation date/time, release version, and build number. User can view the release notes.
 Test Assets Summary

This section provides a summarized and consolidated view of the tests, scripts, and scenarios execution in the system. It contains total tests, achieved tests, locked tests, total scripts, total scenarios, and running tests.

 11Alert Summary

In this section, user can view a summary of the alerts, such as date/time when the alert is generated, severity of the alert, such as critical, major, minor and the description of the alert.

 12Tomcat Heap Memory

In this section, stats on the total heap memory is displayed. Heap memory is a memory used for dynamic allocations. Used heap memory is displayed (in GB) with blue color, and free heap memory is displayed with yellow color along with its percentage.

 13CPU Utilization Vs Load Average

This section displays CPU utilization vs load average in the form of a graph. Various parameters, such as user, system, I/O ae displayed with different colors. The load average among all these is displayed with black color.

 14Available Memory

This section displays stats on available memory (in GB) in the form of a graph. Cached memory is displayed with blue color and free memory is displayed with black color.

 15Disk Space Utilization

This section provides a summary of the disk space utilization by various directories in the system. It contains information such as total space assigned to a particular directory (in GB), free space, used space, along with used percentage.

  1. Under Test Assets Summary section, click Total Scenario(s).

3The Scenario Management window is displayed.

 NoteFor scenario creation, user can also open the Scenario Management window by clicking the Scenarios icon on the left pane. To open a scenario in view only mode, click Total Test(s) under Test Assets Summary section.

The scenario management window contains all the scenarios created in the past. User can view all scenarios irrespective to the project, sub-project or started time using the Show All button. User can also apply filters for getting scenarios that lies in a particular project, subproject, or started at a particular time, such as today/1 week/3 months/12 months by setting the filters and clicking the Apply button. User can also search for a particular scenario using the search box. To reset the filters to default, click the Reset button.

Actions on Scenario

User can perform following actions on a scenario:

Create a Scenario

User can create a scenario by using wizard or advance settings. First, we are describing scenario creation by using wizard. Later, creation of scenario using advance settings is described.

Scenario Creation – Using Wizard


Scenario creation using wizard is a step by step approach for scenario creation with a series of screens. Follow the below mentioned steps for scenario creation using wizard:

  1. Click the Wizard button on the scenario window, the welcome screen of scenario configuration wizard is displayed.

2

2. Post few seconds, various steps for scenario creation is displayed. At first, only the initial step is enabled. Rest other are enabled sequentially on the completion of each step only.

Step – 1: Scenario Name

In this step, user needs to select the project and subproject under which the scenario is to be created. Post that, specify a valid scenario name. First character must be alpha, other characters can be alpha, numeric, dash or underscore. Then, click the Next button to move to the next step.

Step – 2: Scenario Profile (Optional)

In this section, user can select an already created scenario profile (how to create a scenario profile is discussed later). NetStorm have scenario profiles to keep default configurations specific to a subproject at a common place. To use a scenario profile, select the Use Scenario Profile for Scenario Settings check box and specify the project, sub-project, and profile name. Then, click the Next button to move to the next step.

Step – 3: Scenario Group  

Select the Scenario type, either Fix Concurrent Users (FCU) or Fixed Session Rate (FSR). Specify the script from the drop-down list and mention the number of users (in case if FCU is selected) and number of sessions per minute (in case FSR is selected). User can add more records using the Add button. Then, click the Next button to move to the next step. Below is an example of FCU, where 10 users are added in group G1 and 20 users are added in group G2.

Step – 4:  Ramp Up

The Ramp-up phase signifies the action of mounting any sort of operation. This phase is needed, so that in test execution of a scenario, users are ramped by spacing them appropriately. This ramping up reduces overload on Servers.

FCU

Ramp-up can be done by any of the four ways:

  • Immediate Ramp-up

Selecting the Simultaneously option results in all virtual users of the Virtual Group to access site Immediately. This is called Immediate Ramp-up. For example, 80 Virtual users access site instantly for a group.

  • Stepwise Ramp-up

Select a specific number of Virtual users to repeatedly access a site after inserting a time delay (in HH:MM:SS). The users are ramped up in steps. For example, 25 Virtual users are ramped-up followed by next 25 after a delay of 5 seconds, till all 100 are ramped-up.

  • Time Mode Ramp-up

All Virtual users access site after inserting time delay (in HH:MM:SS). This is called Time Mode Ramp-up. For example, 100 Virtual users ramp-up after inserting time delay of (HH:MM:SS). This Time Mode Ramp-up can be further achieved by 2 modes.

    • Linear Time Mode Ramp-up

Users ramp linearly means that the users are created at a constant inter arrival time. All Virtual users access site after inserting a time delay (in HH:MM:SS). System decides to pick a fixed number of users to Ramp-up. For example, System decides to Ramp-up 25 users after every 5 seconds till all 100 users are ramped-up.

    • Random Time Mode Ramp-up

All Virtual users access site after inserting a time delay (in HH:MM:SS). System decides to pick a fixed number of users randomly to Ramp-up. For example, System decides to Ramp-up 20 users after every 5 seconds then ramps up 30 after delay of further 5 seconds and later ramps up 10 users and so on till all 100 users are ramped-up.

  • Rate Mode Ramp-up

Specify a fixed number of Virtual users to ramp-up per Second/per Minute/per Hour.  This Rate Mode Ramp-up can be further achieved by 2 modes:

 NoteThese options are activated by deselecting the Default Rate check box.
    • Linear Rate Mode Ramp-up

Users are created at a constant inter arrival time. Specify a fixed number of Virtual users to ramp-up per Second/per Minute/per Hour. System decides to pick a fixed number of users to Ramp-up. For example, 20 Virtual users ramp-up followed by delay per 1 second, next 20 users ramp-up and after further 1 second delay, 20 more users ramp-up and so on.

    • Random Rate Mode Ramp-up

Specify a fixed number of Virtual users to ramp-up randomly per Second/per Minute/per Hour.  System decides to pick random number of users randomly to Ramp-up. For example, 20 Virtual users ramp-up followed by delay per 1 second, next 30 users ramp-up and after further 1 second delay, 10 more users ramp-up and so on.

 NoteThe default rate is 120 users per minute for our system.

 

FSR

There are following options under this section:

  • Immediate Ramp-up

Selecting the Simultaneously option results in all virtual users of the Virtual Group to access site Immediately. This is called Immediate Ramp-up. For example, 80 Virtual users access site instantly for a group.

  • Time based Ramp-up

All Virtual users access site after inserting time delay (in HH:MM:SS). This is called Time Mode Ramp-up. For example, 100 Virtual users ramp-up after inserting time delay of (HH:MM:SS). This Time Mode Ramp-up can be further achieved by 3 modes:

  • Default Steps: Using this option, a pre-configured steps (i.e. 2) are applied for the sessions’ completion.
  • Steps of specified seconds: Using this option, user can specify the duration for each step.
  • Number of specified steps: Here, user can specify the number of steps to complete a session.

Step – 5: Duration

The Duration phase signifies the time for which the process runs without any change in any settings.

FCU

This Duration phase can further be achieved by 3 modes:

  • Time Mode Duration Phase             

This Time Mode duration phase means that the Scenario runs for a specific defined time. Select the Run for option and specify number of days and time delay in (HH:MM:SS). For example, 100 Virtual users accessing a site remain there for 1 day, 01:12:24, i.e., 01 hour, 12 minutes & 24 seconds.

  • Session Mode Duration Phase

This Session Mode duration phase means that the Scenario runs for a specific number of sessions. For example, 100 Virtual users accessing a site run for 10 sessions.

  • Indefinite Mode Duration Phase

In this phase, the Scenario doesn’t stop if Run Indefinite mode is selected. For example, 100 Virtual users accessing a site remain there for indefinite time.

 NoteThis is the default option.

FSR

There are following options under this section:

  • Time Mode Duration Phase             

This Time Mode duration phase means that the Scenario runs for a specific defined time. Select the Run for option and specify number of days and time delay in (HH:MM:SS). For example, 100 Virtual users accessing a site remain there for 1 day, 01:12:24, i.e., 01 hour, 12 minutes & 24 seconds.

  • Indefinite Mode Duration Phase

In this phase, the Scenario doesn’t stop if Run Indefinite mode is selected. For example, 100 Virtual users accessing a site remain there for indefinite time.

 NoteThis is the default option.

Step – 6: Ramp Down

The Ramp-down phase means a gradual decrease in number of Virtual Users from system. This is reverse of Ramp-up Phase.

FCU

Ramp-Down can be done by any of the three ways:

  • Immediate Mode Ramp-Down Phase            

Selecting the Simultaneously option results in all virtual users to be removed from the site Immediately. For example, 100 Virtual users accessing a site are removed from the system immediately.

  • Step Mode Ramp-Down Phase

Select a specific number of Virtual users to repeatedly removing from the system after a time delay (in HH:MM:SS). For example, 25 Virtual users are ramped-down followed by next 25 after a delay of 5 seconds, till all 100 users are removed from the site.

  • Time Mode Ramp-Down Phase

All Virtual users are removed from system after a time delay (in HH:MM:SS). This Time Mode Ramp-Down can be done by any of the two ways:

    • Time Mode Ramp-down – Linearly

All Virtual users are removed from system after inserting time delay of (HH:MM:SS) in a Linear mode. System decides to pick a fixed number of users to Ramp-down. For example, System decides to Ramp-down 20 users after   every 5 seconds and so on till all 100 users are ramped-down.

    • Time Mode Ramp-down – Randomly

All Virtual users are removed from system after inserting time delay of (HH:MM:SS) in a Random mode. System decides to pick a fixed number of users to Ramp-down. For example, System decides to Ramp-down 20 users after every 5 seconds, followed by 10 users in next 5 seconds followed by 30 users ramped down in next 5 seconds and so on till all 100 users are ramped-down.

FSR

There are following options under this section:

  • Immediate Mode Ramp-Down Phase            

Selecting the Simultaneously option results in all virtual users to be removed from the site Immediately. For example, 100 Virtual users accessing a site are removed from the system immediately.

  • Time based Ramp-down

All Virtual users are removed from system after a time delay (in HH:MM:SS). This Time Mode Ramp-down can be further achieved by 3 modes:

Default Steps: Using this option, a pre-configured steps (i.e. 2) are applied for the sessions’ completion.

Steps of specified seconds: Using this option, user can specify the duration for each step.

Number of specified steps: Here, user can specify the number of steps to complete a session.

Step – 7: Page Think Time

Page Think Time is the Page View Time (after a page is downloaded).

FCU and FSR

There are following options under this section:

Think Time Options

  • No Think Time: No time is spent in viewing the pages. This is the default option selected. 
  • Random (Internet type distribution) think time with median of value specified in seconds: The think time is taken randomly in internet type distribution pattern with median of the value specified. For internet type distribution, median is roughly around ¼th of the mean.
  • Constant think time of value specified in seconds: By selecting this option, constant think time can be taken for each page. The time needs to be specified in seconds.
  • Random (Uniform distribution) think time from specified range in seconds: It randomly takes the value of think time from the range specified in uniform distribution.
  • Custom think time returned by C method: Enter the method name.

Override Recorded Think Time

This setting overrides the setting of the page think time for the particular pages. To override recorded think time, following options are available:

  • Use recorded think time: If user selects this option, the default think time of the script is applied.
  • Multiply recorded think time by some value: On selecting this option, user has to provide some value (number) so that the given page think time is multiplied by the value provided in this textbox. By default, it is 0. 
  • Use random percentage of recorded think time: On selecting this option, user needs to provide the minimum and maximum % value so that the page think time is in between the minimum and maximum % of the above provided page think time.

Step – 8: Session Pacing

Session pacing is an interval between two sessions executed by a virtual user.

FCU

There are following options under this section:

Start New Session

This specifies when the next session is started after a VUser completes previous session. It can have one of the possible values:

  • As soon as the previous session ends: The new session begins as soon as possible after the previous iteration ends. This mode is good for loading the SUT maximally. (This is the Default mode)
  • After the previous session ends: The new session starts after the end of previous session. There are following options:
    • With fixed delay: The next session is started after a fixed delay. Specify the delay in seconds.
    • With random (Internet type distribution) average delay: The delay is random average delay of the time specified in seconds.
    • With random (Uniform distribution) delay: The delay is of random but uniform distribution and within the range specified in seconds.
  • Once every interval (Provided that the previous session ends by that time else next session starts as soon as previous session ends):
    • At fixed interval: The next session starts after a fixed interval of time specified in seconds.
    • At random (Internet type distribution) average interval: The delay is random average delay of the time specified in seconds.
    • At random (Uniform distribution) interval: The delay is of random but uniform distribution and within the range specified in seconds.

Example: Consider a situation where previous session took 10 seconds and user has pacing time of 15 seconds. In this case, next session would be started after 5 seconds of completing the last session. This mode tries to keep the average session rate same even if the server response time changes. This is more similar to real life situations where the typical session rate (sessions/hours) does not change for an application if the response time is increased. If the last session takes more than pacing time, next session would be started immediately after completing previous session.

Introduce delay before first Session too (By randomized mean pacing time): By enabling this check box, a delay can also be applied before start of first session. This delay is calculated by randomized mean pacing time.

Simulate a new user on each session: By selecting this option, a new user is simulated on each session.

  1. This completes the scenario creation using wizard and scenario summary report is displayed.

4. Click the Save button to save the settings. A confirmation message is displayed that scenario has been successfully created.

15

5. Click the Close button to close the window and exit from the wizard. Clicking the Advance Settings button navigates the user to the scenario settings window.

Create Scenario – Having Developer Capability

If you log in to NetStorm using the developer capability access, the NetStorm landing screen is displayed. In this window, you can analyze test results, view the list of scenarios, add scenarios, and view reports such as the summary report and performance report.

The NetStorm landing screen consists of the Test Executed and Scenarios section. You can perform the following tasks:

  • Analyze the Executed Tests: The Test Executed section provides information about est runs, scenarios names, the status of test run, and view the Performance Report/Summary Report/Pass-Fail Report of executed test runs or open the Web dashboard for detailed analysis. You can analyze the status of selected test runs along with Performance Metrics.
  • Manage Scenarios: In the Scenarios section, you can:
    • Add new scenarios by clicking the Add button.
    • Select and run a scenario from the list of existing scenarios.
    • Clone the scenarios from GIT Repository by clicking on the GIT clone icon.
    • Open a scenario in the Editor mode or Advanced mode and add check profiles.

Scenario Creation – Using Advance Settings

To create a scenario, go to Scenarios from the left pane and click the Create button, the Create Scenario dialog box is displayed. Specify the details, such as project, sub-project, scenario name, and profile to be used (optional), and click Next.

This creates the scenario and displays the Scenario Settings window where user can perform various settings for the scenario.

Copy a Scenario

Here, user can create a copy of the scenario using the Copy button. For this, user for needs to select a scenario for which a copy needs to be created. Post this, on clicking the Copy button, the Copy Scenario dialog box is displayed.

Now, select the project, sub-project to which scenario needs to be copied. Specify the scenario name in the Copy To section, and click the Nest button. The scenario gets copied and scenario settings window is displayed.

Delete a Scenario

To delete a scenario, first select the scenario, and click the Delete button. System prompts for a confirmation of deletion. Click OK, the scenario gets deleted from the scenario list.

View Script

User can view the script used is the scenario creation. To do this, select he scenario and click the View Script button. The script gets displayed on the Script Manager window.

5

Save Scenario as Profile

User can also save a scenario as a profile. To do this, select a scenario, and click the Save Scenario As Profile button. A dialog box is displayed to provide project, sub-project, and profile name. After specifying the details, click the Save button.

The scenario gets saved as a profile.

Version Commit

It creates the backup file of currently selected scenario file with latest version. To perform this activity, select the scenario from the list, and click the Version Commit button. A dialog box is displayed.

Specify the comments and click the Commit button.

Version Log

In this feature, user either can update any version of committed scenario file with new changes or can delete the committed file. To perform this activity, select a scenario and click the Version Log button. A dialog box is displayed.

8

Actions

  • Update: This button is used to update the current version of the scenario.
  • Diff: This button is used to get the difference between two scenario versions.
  • Delete: This button is used to delete a scenario version.
  • Close: This button is used to close the window.

Scenario Schedule

The tasks are executed automatically based on the preconditions, inputs, and the scheduled time. In Scheduler Management, user is asked to provide some pre-conditions for starting a test. Once conditions are provided, user is required to specify the email id to make aware that test has been started (in case user is not available at time when test has been started).

Once all the details regarding the test is provided, a time to schedule that task is provided to user. Once the time matches with server time, the task is executed or in simple words, the test gets started.

To perform this activity, select a scenario and click the Scenario Schedule button. A dialog box is displayed.

This dialog box contains two tabs – Scheduler Management, and Create Task.

Scheduler Management: Under this section, all the scheduled tasks are displayed with the following details –  task type, task name, description, schedule time, schedule expiry time, status, and action that could be performed on the task, such as edit, delete.

Create Task: In this section, user can create a task and schedule it for its execution. To perform this activity, click the Create Task tab. The Scenario Schedule window is displayed with first section as Task Description.

10

Specify the task description, such as task name, project, sub-project, scenario name, and scenario description. Then, click the Next button, the Scenario Parameter section is displayed.

Specify the following details:

Pre-check Parameters

  • Timeout: Denotes the timeout in seconds.
  • Retry Count: Denotes the number of retries.
  • Retry Interval: Denotes the interval between each retry.

Post- check Parameters

  • Wait Time: This is the waiting time.
  • Forcefully: There are following options under this – don’t start a new test, stop previous test and start new test after wait time, start a new test in offline mode.

Once the pre-check and post-check parameters details are specified, click the Next button. The section to add user’s mailing details is displayed. This is used to make the user aware about the schedule details on email.

11

Specify the user email ID, subject, and body of the email. In the body section, use the predefined parameters, such as test number, start time, and end time. This step is optional and can be skipped by clicking the Skip button. User gets navigated to the next step of the scenario schedule management.

12

This section displays the summary of the task scheduler. It is divided into two sub-sections – task description, and scenario parameters. Expand the sub-sections to see the details. Next, click the Finish button. A message is displayed that task is added successfully.