Does jmeter work with webseal? - jmeter

I've trying to make some jmeter test to work with webseal.
The test were working fine without it even in https but with webseal I get 302 and 404 error on some of my httprequest while other work just fine.
But according to this page : http://90kts.com/2008/10/27/performance-testing-spnego-or-kerberos-with-loadrunner/
jmeter and webseal don't work.
I'm probably reading it wrong but I can't seem to find info about the usage of those 2 product together.
Anybody have experience using jmeter and webseal or should I look for a alternative load test product ?

the problem is neither jmeter or webseal but how badboy was exporting the request in jmeter.
The implementation fo the http request need to be httpclient4 in order for the login to work but badboy was settin git to java by default.
And the path saved by badboy is plain wrong, it giving the sub path were has the initial request (which was working) was a level higher.
working: /parent_path/Apps/servlet
badboy: /Apps/servlet
however this seem to not be a problem in a environement without webseal.

Related

Jmeter API testing using csv input as post request in localhost

I tried to run a POST method for API testing in JMeter, I have sent the parameters as needed in body using a csv file. It works with https url(domain url) but not working in localhost. In localhost, requested body is showing blank. Please help me to resolve this issue.
There should be no any difference between local and non-local URLs so most probably you made a configuration mistake somewhere. We cannot state where exactly without seeing the test plan so I would suggest:
Inspect request and response details using View Results Tree listener
Ensure that the variables originating from the CSV Data Set Config really exist and have their respective values by adding a Debug Sampler and seeing what variables are there.
Check jmeter.log file for any suspicious entries. If it doesn't say anything meaningful you can try increasing logging verbosity to DEBUG level.

Jmeter 5.4.1 failing for 500 response - Internal Server Error - while trying to login

I have recorded script by using Blazemeter. It worked fine for the first day. Now when I am running the same jmx file, it gives me Response code 500.
Please help me to understand what I did wrong.
Sampler Result:
This is how my parameters are posted at login.
BodyData tab does not open for me.
Login parameters:
When you say that it ran successfully yesterday and today it is failing, there is some parameter like session / token that was valid for like 12 hours / 24 hours and now it has expired. You will need to identify that and parameterize it. I cannot help you much right now as I don't know what is that variable value and how does it differ each day. Perhaps checking with developers will help.
It seems you're trying to test a secure web service and most probably there is a current timestamp included somewhere in your request body so the request was passing when it was more or less "recent" and after some time the request became invalid due to expiration.
I cannot state where exactly the problem is and how to fix it by looking at partial screenshot so I can give you only a generic piece of advice: consider using WS-Security Plugin for JMeter for adding the relevant SOAP header containing up-to-date information like timestamp and eventually a signature.
More information: Running SOAP WS-Security Load Tests in JMeter

Not getting proper response in the tree table after performing login scenario using JMeter

I just started to use JMeter with the tutorial (for a sample website), which returns clear response data.
But, when I started to use in one of my projects, I saw the response was encrypted in View results in tree.
So can anyone provide solution for it? This was the response i was getting
I doubt you haven't check marked 'Use this proxy server for all protocols' while creating manual proxy configuration. By checking/ ticking that check box it will allow you to record the scenarios and also it gives you a proper response.
and I also doubt that you are getting proper server name. By doing the above step it will solve your problem

Data entry through Jmeter not reflected in UI of application

I'm using Jmeter to perform load test on Moodle application
I followed the below steps to replicate a simple "add company " test scenario
1: Recorded the browser actions through HTTP Test script recorder and created a test plan with thread user of 1
2: Added HTTP Cache Manager,Added regular expression extractor for retrieving dynamically generated session for login HTTP request.
For Http request of adding new company, addded user parameters containing new company name
I run the test, everything seems ok in the view results tree- response section (response code: 200,response message:OK), all the required variables are passed in the HTTP POST
PROBLEM: New company added through Jmeter test is not reflected in UI of the moodle action
Can any of you please let me know
Is there something I could be missing or anyway I can debug the problem?
P.S: I'm new to Jmeter and looked around a lot for data inputted through Jmeter not being displayed in the UI of the web application,dint find useful results.
The answer to questions of this sort is almost always that you missed some necessary dynamic value besides session ID which you did catch.
An HTTP200 response just means the server returned a "good" response. Which could also happily contain an error message.
I would check the actual html body of the returned response for any errors. Checking the log on the server side can give you clues to what went wrong sometimes. You should also try adding a cookie manager.
Run your test with 1 virtual user in GUI mode with View Results Tree listener enabled and inspect responses to see where your scripts fails. My expectation is that you simply cannot log in.
See Moodle-JMeter-LoadTest.jmx file for reference, it uses XPath Extractor to get session key and course id.
I don't think you can test using JMeter. Try JUnit Test cases instead http://jakarta.apache.org/jmeter/usermanual/junitsampler_tutorial.pdf

Need to debug recorded jmeter script

I recently recorded a test script in Jmeter intended for use as a load test script (using this handy set of instructions. The recording itself worked great and I even figured out how to grab and parametrize the session ids and timestamps. However, if I run the recorded steps just as they were recorded some of them don't work -- they generate "500--Server encountered and internal error ...nested exception is java.lang.NullPointerException" The failing steps are all Ajax calls that populate sidebar elements. If I copy the request GET call (Request tab, ViewResultsTree) and paste it into a browser I get the exact same error. Do I need to record my script differently, or hand-code the ajax calls? Other, earlier steps work correctly and send the expected POST data, so it isn't the application under test or forgotten proxy settings. Currently running against Firefox 3.6.10
Any suggestions on how I can debug this would be greatly appreciated.
The first thing I'd do is determine if the java.lang.NullPointerException is happening on the client side (JMeter) or on your server. If it is happening in JMeter, than something is terribly wrong with either your script or with JMeter.
But assuming that the error is encountered on your server, then looking into the cause of the exception may shed light on what is wrong with the request issued by JMeter. Do you have access to the code where the exception is thrown?
I would also recommend comparing the request in the recording with the request that generated the error. You may need to determine which parts of the request are session-specific and ensure those fields are populated correctly.
It sounds like Jmeter isn't executing the AJAX calls, and this can be fine depending on your site. Can you simply do an HTTP request to get the pages the AJAX calls populate?
I would recommend reading this post, as it looks pretty good.
I've seen that situation caused by a few things:
a page is required to load and be cached BEFORE making the failing request;
the failing page needs to automatically redirected to work properly;
the failing page has sub-requests JMeter failed to record. Devs can help with this.
Hope this helps.

Resources