Need help with WAPT 6.0 user session emulations Inconsistencies found when making virtual user profiles.
#1
Posted 22 April 2010 - 08:58 PM
We have an ASP.NET application that uses forms authentication, and was developed as a Single Sign On application. Users that visit the Login screen can click on a check box to use automatic sign in which pulls their windows identity and authenticates them to our application. We also have a full audit system that tracks and logs a user's movement through the system. Here is my dilema. When setting up a user profile that simply logs in to the application and logs out there is a major inconsistency in how the recorder works and the actual test run.
Here is an example;
I have 3 accounts (LoadTestUser1, LoadtestUser2, and LoadTestUser3)
I create a profile that has all 3 accounts, with passwords, listed under Integrated Windows Authentication. I am running the WAPT software as LoadTestUser1 in order to utilize windows authentication for the actual recording, otherwise, it simply pulls my own windows identity and I need the recording to use one of the load test accounts. Now, the steps for this recording are;
1. Navigate to LogIn page
2. Start WAPT recording
3. Check the auto sign in box
4. Click the Login button.
5. Once logged in and on the default home page, click the LogOut button.
6. Once back at the LogIn screen, press Stop Recording.
After the initial recording is done, I go and check my auditing database to see if the actions were recorded, and they are. I get audit trails for the following;
1. LogOn
2. LogOff
3. Session End
However, when i run the actual test, for each user listed I only get one event audited;
1. LogOn
The user profiles never show that the LogOff event was fired during the test run even though during the recording phase it was proven to have occurred. Any insight here would really help. It seems like following login, no other actions occur for the listed users in the profile. How do I fix this?
#2
Posted 23 April 2010 - 08:14 AM
WAPT Project Manager
SoftLogica LLC
Office: +7-383-335-6692
Toll-free: 1-888-364-6797 (for US only)
Time zone GMT +6, EST +11
E-mail: support@loadtestingtool.com
http://www.loadtestingtool.com
#3
Posted 23 April 2010 - 03:22 PM
#4
Posted 26 April 2010 - 10:12 AM
WAPT Project Manager
SoftLogica LLC
Office: +7-383-335-6692
Toll-free: 1-888-364-6797 (for US only)
Time zone GMT +6, EST +11
E-mail: support@loadtestingtool.com
http://www.loadtestingtool.com
#5
Posted 26 April 2010 - 02:47 PM
#6
Posted 27 April 2010 - 06:10 AM
WAPT Project Manager
SoftLogica LLC
Office: +7-383-335-6692
Toll-free: 1-888-364-6797 (for US only)
Time zone GMT +6, EST +11
E-mail: support@loadtestingtool.com
http://www.loadtestingtool.com
#7
Posted 27 April 2010 - 03:32 PM
#8
Posted 28 April 2010 - 02:04 AM
It's a bug, we are fixing it.
Give me your scenario, profile and full log or send they to support@loadtestingtool.com. I'll explain how to add a POST request in your case.
WAPT Project Manager
SoftLogica LLC
Office: +7-383-335-6692
Toll-free: 1-888-364-6797 (for US only)
Time zone GMT +6, EST +11
E-mail: support@loadtestingtool.com
http://www.loadtestingtool.com
#9
Posted 28 April 2010 - 06:23 PM
Give me your scenario, profile and full log or send they to support@loadtestingtool.com. I'll explain how to add a POST request in your case.
Sergei,
I have attached the requested files. Please let me know what I can do. Also, any idea when the reported authentication bug in WAPT Pro 2.0 Beta will be fixed? Thanks.
Attached File(s)
-
Test_Scenario_Files.zip (28.01K)
Number of downloads: 10
#10
Posted 29 April 2010 - 10:28 AM
In page_2 I created two variables and used their values for __VIEWSTATE and __EVENTVALIDATION parameters in page_3. I’ve attached the changed profile.
Attached File(s)
-
Profile1.wpp (62.21K)
Number of downloads: 7
WAPT Project Manager
SoftLogica LLC
Office: +7-383-335-6692
Toll-free: 1-888-364-6797 (for US only)
Time zone GMT +6, EST +11
E-mail: support@loadtestingtool.com
http://www.loadtestingtool.com
#11
Posted 30 April 2010 - 07:12 PM
Your presented solution had no effect. The previous scenario I sent involved automatic sign in which works by pulling the current windows identity for authentication. I have attached a revised scenario which uses manual log in. I am still having issue with the log out process being recorded properly. Please review and provide any feed back. Thanks.
Attached File(s)
-
Test_Scenario.zip (14.59K)
Number of downloads: 2
#12
Posted 04 May 2010 - 10:38 AM
Your presented solution had no effect. The previous scenario I sent involved automatic sign in which works by pulling the current windows identity for authentication. I have attached a revised scenario which uses manual log in. I am still having issue with the log out process being recorded properly. Please review and provide any feed back. Thanks.
I looked to the log and I have no idea why logon failed. Could you provide an access to your site?
Also we've fixed the issue with authorization in WAPT Pro 2.0. You can download it from http://www.loadtestingtool.com/forum/builds/WAPTPro2.0.zip
WAPT Pro 2.0 has a new recorder. Now you can record and compare the recorded and performed requests and find the differences.
WAPT Project Manager
SoftLogica LLC
Office: +7-383-335-6692
Toll-free: 1-888-364-6797 (for US only)
Time zone GMT +6, EST +11
E-mail: support@loadtestingtool.com
http://www.loadtestingtool.com
#13
Posted 04 May 2010 - 10:39 PM
Also we've fixed the issue with authorization in WAPT Pro 2.0. You can download it from http://www.loadtestingtool.com/forum/builds/WAPTPro2.0.zip
WAPT Pro 2.0 has a new recorder. Now you can record and compare the recorded and performed requests and find the differences.
First off, the new version of the WAPT Pro 2.0 Beta is now working, the integrated authentication issue appears to be resolved. That being said, when I used the recorder to create my profile, and ran the test in WAPT Pro 2.0 Beta, everything worked as expected. I duplicated the profile in WAPT 6.0 and ran the test and it continued to have the same issue. One of the things I noticed that is different is that in WAPT Pro, you give the option to select the POST Parameter type. This was not allowed in WAPT. Other than this, I can find no differences between the profiles. I need to know why identical profiles are working in one version and not the other. Could the POST parameter type be causing the issue?
#14
Posted 05 May 2010 - 10:36 AM
WAPT Project Manager
SoftLogica LLC
Office: +7-383-335-6692
Toll-free: 1-888-364-6797 (for US only)
Time zone GMT +6, EST +11
E-mail: support@loadtestingtool.com
http://www.loadtestingtool.com
#15
Posted 05 May 2010 - 02:49 PM
I have attached the requested files. Please advise on what I should try next. I'm literally at a loss here.
Attached File(s)
-
My_WAPT.zip (21.26K)
Number of downloads: 2 -
My_WAPT_Pro.zip (54.83K)
Number of downloads: 1
#16
Posted 06 May 2010 - 10:07 AM
WAPT Project Manager
SoftLogica LLC
Office: +7-383-335-6692
Toll-free: 1-888-364-6797 (for US only)
Time zone GMT +6, EST +11
E-mail: support@loadtestingtool.com
http://www.loadtestingtool.com
#17
Posted 06 May 2010 - 02:42 PM
Sergei,
Well slap me around and call me Susan....Houston, we have lift off! I was using the Dec 2009 build of WAPT 6.0. Apparently this was the problem because the minute I used the April 2010 build, it worked as advertised. My only suggestion at this juncture would be to have a better method for informing clients of new build releases. I've lost weeks on this and it wound up being a simple build issue. Anyhow, thank you for sticking with me through this.
One Note, while the recorder does infact no record the log out action, I noticed a little strange behavior. My profile ends by clicking the LogOut button and firing a logout event. This returns the user to the login screen but does not trigger any further behavior. For some reason, WAPT attempts to log in again. I know this because I have a full audit trail that runs on my system so important events are tracked. After every logout event run by WAPT, I get an immediate Login event that fails. When running the app outside of the WAPT software this behavior is not observed. Any ideas on the cause of this glitch. it's not such a big deal that I cannot complete my load tests, but it is rather odd.

Help











