Scenario Design And Execution
(FCU-Simple,Group Based)
1
FCU
Advance
Simple
Scenario
Based
Group
Based
Scenario
Based
Group
Based
2
 Scenario
groups (Mandatory. At least 2 groups)
 Scenario schedule
 Global settings
 Group based settings
 User profiles
 Server mapping
3







Session pacing are used to give a difference between the different
sessions. Session pacing has the different mode to applying between the
session:Fixed delay of session
Random delay of session
Random delay of min to max time.
Sessions Pacing is used give a time difference between the sessions, how
much implemented in the scenario. We can easily differentiate the time
difference between the sessions and can observe the session pace by the
progress report of the test of that scenario
Each session may be assigned a default session pace . If a session pace
is not associated with the sessions, default session pace would be used
for all session completed in a scenario. Session pace is a group based
keyword.
SyntaxG_SESSION_PACING <Group Name> <Session Mode> <Session Time>
Default value of session pacing is 0 seconds for each session.
4




It is really un-realistic for any real user to just keep clicking the
pages one after the other without pausing to look at it. After a page
is accessed, the user would spend some time viewing it. The average
viewing time depends upon the page contents & the user familiarity
of the page.
Each Page may be assigned a think time. If a think time is not
associated with a specific page, default Page think would be used for
such pages. Page Think Time is also called the Page View Time (after
a page is downloaded). Page think time is a group based keyword.
SyntaxG_PAGE_THINK_TIME <Group Name> <Page Name> <Thinking
Mode> <Think Time>
Default value of think time is 0 seconds for each page.
5
5
Scenario Requirements
6
 Scenario
Type: FCU scenario
 Scenario Groups
Total Users - 300
Number Mode
 Two groups with Number as shown
gp1 for Script hpd_tours –100
gp2 for Script static1K –200
7
 Schedule
consists of following phases for group gp1:
Start phase – IMMEDIATELY
Ramp Up – 50 per minute RANDOMLY
Stabilization – 0 seconds
Duration – 5 Minutes
Ramp Down – Stop ALL in 1 minute
Session Pacing – once every 10 seconds
Page think time – constant PTT of 0.1 seconds
8
 Schedule
consists of following phases for group gp2:
Start phase – 1 Min
Ramp Up – 5 Min LINEARLY
Stabilization – 0 seconds
Duration – 10 Minutes
Ramp Down – 120 users per minute
Session Pacing – once every 5 seconds
Page think time – constant PTT of 1 second
9
Scenario Design
10
Select the Project and Subproject and enter Scenario name and click on
create button.
11
•Click on the add group button and add gp1.
12
Double click on start phase
Click on ‘Start immediately after scenario begins’
13
Double click on Ramp up phase
Give rate 50 vusers/ minute randomly.
14
Select the Stabilization phase and give the time of 0 sec to stable our
scenario
15
Select the Duration phase and give the time of 5 min to run the
scenario
16
Select Ramp down phase
Click time mode option and give time of 1 min(linearly))
17
Group Based Settings for gp1 -> Page
Think Time
)
Give a constant PTT of 0.1 seconds.
18
Group Based Settings for gp1 ->
Session pacing
)
Give session pacing at a fixed interval of 10 seconds.
19
Click on the add group button and add gp2.)
20
Double click on start phase
Click on ‘Start after scenario begins’ and enter the time as 1
minute.
21
Double click on Ramp up phase
Click on time mode option and give time 5 min(linearly)
22
Select the Stabilization phase and give the time of 0 sec to stable our
scenario
23
Select the Duration phase and give the time of 10 min to run the
scenario
24
Select Ramp down phase
Click time mode option and give time of 2 min(linearly))
25
Group Based Settings for gp2 -> Page
Think Time
)
Give a constant PTT of 1 second.
26
Group Based Settings for gp2 ->
Session pacing
)
Give session pacing at a fixed interval of 5 seconds.
27
After scenario is designed, make sure you save it.
28
Scenario
29
Expected Results
30
Group
Name
Start
phase(i
n min)
Ramp
Up(in
min)
Stabiliz
e
Duratio
n(in
minute)
Ramp
Total
Down(in time(in
minute) minute)
gp1
0
2
0
5
1
8
gp2
1
5
0
10
2
18
Total time taken in scenario execution = 18 minutes(expected)
Since we are using simple-group, total time taken will be maximum
of the total time taken individually be each group.
31
From the progress report we can see that the total
time taken is 18 minutes.
32
Total Connections
After 1 min total users in the system are 10 from gp1 and since we are
using hpd_tours script for group gp1 then there will be only 40 connections
will be after 1 min( since for each user in script hpd_tours we have 4
connections).
After 6 min total users in the system are 260. Out of 260 users, we have
from group gp1 -60 users, then total connections are 240 due to hpd_tours.
From group gp2-200 users, then total connections are 200 due to Static1K.
( since for each user in script static1K we have 1 connection).
Then total connections after 6 minutes are 440.
After 10 minute total users in the system are 300. From group gp1-100
users, then total connections are 400 due to hpd_tours. From group gp2200 users, then total connections are 200 due to Static1K.
Total connections after 10 minutes are 600.
33