I have a requirement on IBM MQ publishing messages per required amount of time,below is example
5 MQ requests per second,How I achieve this in LISA 7.5.2.
Any help please.
Have you completed the creation of your test, so it loads your set of filenames as the dataset, then opens a data file and reads the XML, making a property of that and using the property in your MQ step?
If not, that's the place to start. Create yourself a test that operates functionally. Can you perform functional testing of the MQ server application using the test you've created?
When you're happy with the test, make sure to remove any "final_step-to-first_step" iteration you might have added for testing that the dataset loads from a different file every time, and save it. You want to remove the iteration because your staging document will do that.
I would make sure the data files are stored in your DevTest project folder, in the "Data" folder. If you do this, DevTest can package your data files with your test when it sends it to the execution engine.
Only then should you create your staging documents. You want one for functional testing (1 user) and one for your load profile (choosing any of the other load patterns). I don't know what values to provide, as I don't know your test case. At such a light load as you mention, it shouldn't take much more than choosing any of the load profiles and typing 10 & 1m into the pacing boxes.
After this, you'll want to investigate the other tabs (metrics, reporting, etc) and you will want to create a Suite to combine your test with your staging document.
There should be videos of this stuff, somewhere, but I don't know exactly where - perhaps some helpful soul will see this thread and link us to them?
The Staging Document is where you throttle back the number of transactions per second. It's "Test Pacing" in the top-right of the Staging Document man tab
This document is for v9.1, but I don't recall that functionality changing since before v7.
Staging Document Editor - Base Tab - DevTest Solutions - 9.1 - CA Technologies Documentation
For my understanding on your response,
Yes we have Test Pacing section where we also have 'Number of Test Executions' and 'Per Given Time' .
If I give Number of Test executions = 5
Per Given Time = 1sec
So test will execute with 5 requests or 5 times if yes then it will execute each time with same request .
Then how do I change request each time.
Not quite. It's the pacing of the test run that uses the staging document. It can be associated with any number of tests doing any number of things. As long as your test workflow step isn't set to "quiet", it'll be included in the pace throttling indicated in the staging document.
So, if you have one test that executes two MQ transactions, data-driven so they are sending different data to the queue(s) each time, and you create your staging document as weighted (short ramp-up, short ramp-down, long execution) with 10 virtual users and a pacing of 5 tps, you will get up to 5 transactions of various types using various data every second. The pacing is to throttle back transactions per second, so you will want to make sure your test workflow steps would normally send more than 5 tps; i.e.: have a short think time associated with them or increase the number of virtual users.
Thanks RICK for your continuous support,
also please guide me on the below exact requirement
I have external folder in d drive which contains 20 XML messages as test data for my script ie;data-Driven which you mentioned above.
I want to run the script for particular tps let's say 10 per 1 min
Now could you please guide me what are the values to provide for Pacing and Load Pattern option-weighted avg pattern.
Please don't hesitate for my queries,I am just a baby steps in using LISA for LOAD testing.
Thank you very much RICK.
I have already created test such as read file names and and save the file content in one property and sending to MQ step.
Monday I will check with staging doc and let you know RICK.
Again Thanks for your support.
RICk I have all the above steps and still unable to run the test completely,test went to stuck after some time and fails due sleep time of execution due to CPU usage reached to 100%.
Retrieving data ...