I'm testing an API and want to make sure it returns the expected result. However the expected result is too big. Every time I tried to copy and paste it in 'Patterns To Test', it got frozen. Now I save the expected result into a file and in the 'Response Assertion' I want to compare the API return against the file to check if they are same.
How can I do that?
You can use __FileToString() function instead of copying the file into the "Patterns" section of the response assertion.
If your response is really big I would recommend switching to MD5Hex Assertion
Tick Save response as MD5 hash box at the "Advanced" tab of the HTTP Request sampler
Calculate MD5 checksum of the file, the approaches differ depending on the operating system and software you have, as the majority of the world is on Windows I'd suggest WinMD5Free, check out How to Use JMeter Assertions in Three Easy Steps for other options and more detailed information
Replace Response Assertion with MD5Hex Assertion and use the checksum from step 2 instead of full response
The idea is that equal strings have equal hashes and comparing 2 short hashes is faster operation than comparing 2 big strings
Related
I am new to JMeter and scripting overall.
Here's my scenario - My response from the HTTP request generates data every second and the response gives the timestamp along with other data. I have to identify if there is any gap in the timestamp sequence just to identify if there is any gap in the data overall.
Example of my response is attached (timestamp highlighted).
How can I achieve this? The whole idea is that the data should be present for every second, and missing data needs to be identified.
Post Note - There will be thousands of rows depending on the start and end time I am passing in the request, but since JMeter limits the data row to 1000 rows only and my data is going to be more than that, how can I loop my request so that the end time passed in my previous request becomes the start date of my next request and the request becomes a 15 minute time range request which will generate 900 records.
Please let me know if more details is needed or if I don't make any sense.
Please see the attachment as well.
Any guidance will be really helpful.
Thank you!
Keshaventer image description here
I'm new to scripting so don't have much idea on how to proceed with this and how to accomplish this.
I'm not very good by parsing incomplete JSON by looking at screenshots so I can only provide a generic answer:
You can create custom pass/fail criteria using JMeter Assertions in general and in your case JSR223 Assertion in particular
Response body can be fetched as prev.getResponseData() where prev stands for the previous SampleResult
Once done you can use XmlSlurper to extract data attribute values and store them into some form of Array
And finally iterate the array and check if the next item is 1 second ahead of the previous
We have script, jssr preprocess which will copy the file from one bucket and paste it to another bucket in Amazon s3and http request which will take the file and do further processing.
Before copying file we do renaming filename with timestamp(function help builder). Everytime we do performance testing it has to pick unique file name.
But when I run send requests for 5 minutes, timestamp remain same, it's taking first timestamp through there is some second difference between each request. Is there any way each request to generate unique timestamp within jssr preprocessor
It's not very possible to come up with the solution without seeing your "script".
Blind shot: if you're using __time() function inside the JSR223 PreProcessor only first occurrence will be evaluated, on subsequent executions the same value will be used.
If this is the case either move the __time() function to the Parameters input field or use System.currentTimeMillis() function instead
Demo:
More information:
JSR223 Sampler Documentation
Apache Groovy - Why and How You Should Use It
Few of the token values are changing compare to response to replaced in the script. please let me know how to over come this issue
1st value
Recorded Server response in JMeter recording log
VI1js8eNsTKaakYaEsdhPPg+nlPY2SL6/0RoyxBL1BE=
Replaced value in the JMeter script
VI1js8eNsTKaakYaEsdhPPg%2BnlPY2SL6%2F0RoyxBL1BE%3D
2nd value
Server response
C/K6QoR6Qjk/pLQAyvQ5FiRXFK9BAxeRJAEDJ+BGA+w=
Replaced value in the JMeter script
C%2FK6QoR6Qjk%2FpLQAyvQ5FiRXFK9BAxeRJAEDJ%2BBGA%2Bw%3D
Please hlep to to over come this issue.
Thanks
Raghav
Most probably there is some form of encryption/decryption logic which is applied to certain request parameters, it's not possible to guess the algorithm so if you don't know it you need to ask around.
Once you will know what exact encryption algorithm is being applied - you should be able to perform the same either using __digest() or __groovy() functions
I could see a random number calculated in the response as below
var rndnum = Math.floor(Math.random() * 11);
The subsequent request is expecting this rndnum to be passed. Unable to see the number generated in the response. If I just pass some random number, the response time is high and incorrect.
Any help?
You need to store the result in a JMeter variable using:
vars.put(‘rndnum’, ‘’+rndnum);
There are 2 options:
rndnum variable is present in the response. If so, you should be able to extract it using Regular Expression Extractor.
rndum variable is NOT present in the response. If so you are free to generate a random number between 0 and 10 via JMeter's __Random() function like:
${__Random(0,10,)}
Be aware that according to JMeter Documentation:
JMeter is not a browser, it works at protocol level. As far as web-services and remote services are concerned, JMeter looks like a browser (or rather, multiple browsers); however JMeter does not perform all the actions supported by browsers. In particular, JMeter does not execute the Javascript found in HTML pages. Nor does it render the HTML pages as a browser does
so my expectation is that you should go for point 2.
I am very new to jmeter and have recently started working on it for API load test.
Could someone please explain me why do we need to put assertion in load test, that should have been checked as part of functional test.
Also if I add any assertion as part of my load test it will have an impact on result (avg time, deviation, median etc) which is not correct.
Your thought
The purpose of an assertion on a response would be to insure that you have actually reached the correct destination.
For example if under load you server sends back incomplete responses, or a valid page containing an error message you would never know it without an assertion.
There is always some overhead for processing the assertion, but unless it is performing an excessive number of tests it should be minimal. The assertion is performed on the load generator so if that component cannot handle the additional overhead then the assertions will not be your only concern.
You need to use assertions, but you need to use it carefully. Ensure you use them when required, try to extract as less data as possible.
Follow JMeter tuning tips:
Use Response Assertion or Size assertion, but avoid XML Assertion,
XML Schema Assertion and XPath Assertion
Use Regular Expression Extractor, but avoid XPath Extractor when possible