Need help with StresStimulus? Start here.
VU-Bound uses the same row twice?
|
Unregistered User Posts: 509
7/26/2023
|
We have 2 test cases and 2 credentials datasets. Both datasets use VU-Bound binding.
Below is the approach we are following :
Test Case weight Mix :
1. Test Case A – 20
2. Test Case B – 20
Datasets :
1. TestCaseA_Cred
2. TestCaseB_Cred
Load Policy or test profile:
VUsers – 40
Ramp up – 2 users/ min – 25min
Steady State – 20 min
Ramp down – 10 min
As soon as all 40 people are logged in, we start to experience issues that suggest user credentials have been reused. obtaining session error as a result.
When the test is running under a steady load with all 40 users connected in parallel, everything goes smoothly. This problem only appears when we are ramping up or stepping up the number of users.
|
|
|
0
link
|
|
George @StresStimulus Administrator Posts: 555
7/26/2023
|
To check that StresStimulus uses a different row for every VU, do the following steps:
1. Determine the login session (request) # in Test Case A and in Test Case B
2. In the report, open the Session Test Log (https://support.stresstimulus.com/display/doc57/Querying+the+Test+Log) and query the login session number above for the first iteration and for Test Case A and then for Test Case B
1. Open each resulting session and check the credentials row that was used.
If a different credential row was used in every request, you might be dealing with a concurrency issue rather than a duplicate row issue.
|
|
|
0
link
|
Copyright © 2024 Stimulus Technology