Luminis 3 jMeter script
Attached is a simple Luminis 3 jMeter test plan. To use it, you will need to:
1) Click on the test plan (the purple beaker thing) and edit "user defined variables". Put your school's portal host name in there, plus also change the number of threads (users) you want to test with
2) Create a text file of usernames and passwords that will work and can login to your portal. One user per line, comma separated values:
username,password
The rest should just work. You can type CTRL-R to run the script, and then click on the "Graph Results" to see some interesting stats being graphed. You can click on "View Results Tree" to see the actual URLs being called, and the responses being returned.
This is only the start of a true load test plan - it does not encapsulate all of the classes of users you want/need to simulate. That is the really hard part, and the part that requires a lot of analysis from you. Everyone's portal is completely different, and the behaviour patterns of our users is also different. Each of our respective test plans has to be custom built.
Todd
Thanks For sharing :)
Todd, first of all I want to say "thanks" for sharing this test plan. It is surly great starting point for anyone having to do load testing for Luminis.
This test plan was easy enough to modify and make it work for our system and environment. There is one issue I came across when running this test: "user name/ password combination is not correct" it turned out that the form was expecting 3d parameter uuid, which was not supplied.
To fix this issue I added "Regular Expression Extractor" to /cp/home/displaylogin node with the following values:
Response field to check: Body
Reference Name: UUID
Regular Expression: document.cplogin.uuid.value="(.+?)";
Template: $1$
Match No: 1
I also added third parameter to /cp/home/login node:
uuid - ${UUID}
Looks like this modification fixed my issues with user authentication and I hope this post will be helpful to someone.
Regards,
Vera
Two years of load testing
Wow, hard to believe this post is already two years old. Time flies.
Anyway, yes Sungard is changing their product over time, and introducing new security measures, removing old techniques, and these types of scripts will always need to be evolving. Glad you found it useful!
Todd
Where do you get the users?
Hi Todd,
Funnily enough, I had independently developed an extremely similar test plan on my own before searching the web for some help. If you're still using JMeter to do stress testing, some useful plugins have been released at http://code.google.com/p/jmeter-plugins/. Some features include graphs that aren't super ugly, and a java-based performance monitoring client you can run on the server you're testing to watch resources (JMeter stock monitoring is limited to tomcat servers, for anyone that's wondering).
As we prepare to start testing so we can work everything out before the next registration flood, we have run in to the problem of procuring users to load the CSV with. Our aim is to split 600 concurrent threads across five or six machines running jmeter server. We have come up with a few options-
-Disabling the 1 session per user limit and using a very limited set, duplicated many times.
-Creating 600 new test users, just for the purpose of load testing
-Activating 600 existing accounts, and using those
My question for you is, what did you use for a test user set? Did you just bite the bullet and add 600 users to banner, or is there another way around this problem I'm not aware of?
Users
We created thousands of random user accounts in Luminis, but not Banner. We were not testing SSO in this script, we were only interested in load testing Luminis itself.
Todd
Oh, right. I had mistaken
Oh, right. I had mistaken some other script for the one you've posted here. Sorry about that!