I have question about how to use jmeter for testing outsystems apps ? previously i use jmeter for testing Java API dan Java websocket... but i am new for using jmeter on outsystems... is there any hint for this ?
Hi,
Please check the following links:
Hope that helps.
Nuno Rolo
I had used JMeter once before, to test the performance of the applications. Thou I cannot tell you how to use it (I'm thinking you have some basic knowledge already), but I just want to share about some of the limitations or issues I faced during then.
The network and Elements tab in Chrome inspection tools, most likely will be our best friends for this. And also the Payload tab under the network tab LOL (It's because i'm using regex to capture the values, there are other options which you can explore)
Some of the issues were not solved, so we went to the management to seek waiver, just in case you want to know.
1. Ajax refresh is an issue. For some reasons, which I still couldn't know, sometimes in JMeter it works, sometimes it doesn't. Even thou, in the payload tab under network, whether we using regex101 to capture it, it sometimes doesn't work. I have encounter a situation before, where it works for 1 application, but it doesn't work for the other. And my team actually basically copy and paste it, thinking it will work
2. Too much nested web block is an issue too. Because outsytems have event handling for web blocks, and the passing of values/information between blocks are screens is actually quite unique to outsystems. And JMeter might not be able to capture it. I have a situation before, when i have a web block, passing values to the main web block it's been nested at, and then the value is pass to the screen, before transmitting the value to another web block (which visibility is set as True, when it had received the value).
However, this other web block appear on the screen (in JMeter), however, the value cannot be capture. So we can only see on screen, that this other web block do appears, but the values are not there
3. I had used it to test the Create, Update, Delete actions before. It can worked. As in, literally your database will be amended too. If you are in DEV environment, it shouldn't be an issue. But if you are planning to do it in other environments (hopefully not PROD), please take note that the DB will be updated too.
4. For chrome 'Inspect' HTML or console screen, and JMeter 'Inspect' screen do differs a bit. So sometimes, even thou you have double checked in chrome that the element or ID is there, it does help to check in the JMeter application too. I have encountered before, for some unknown reasons to me again, the regex code is working fine in chrome inspection. But in the actual Jmeter app, the code appears twice. And the one i actually want to capture is the second in line. So Jmeter will keep displaying or highlight it's an issue, or your JMeter results keep failing.
This is all i can think of for now, as it's been close to 1 year since i last touched it. Anyway, my company did reach out the Outsytems, and ask which tool is recommended for performance testing. Outsystems replied JMeter is one of them.
But from my experience, there are still bugs here and there.
Hope my advice can help a bit in your debugging!
** Edited and add-on
If you are using it for performance testing, eg 50 users logging in at the same time, do have 50 unique userId to load into JMeter for testing.
Even thou during development, you might have a lot of screens open using the same UserId and doesn't have any issues, but for JMeter performance testing, it is an issue. What I had experience is that, for the 1st few testing, you might run into errors regarding logging in. But it will clear up after a few times. But your results will be affected already.
And there is an option in JMeter, that if a particular login failed, you can choose to skip and log in again. If you didn't check that CheckBox, JMeter will continue testing, and the rest of the screens will just end up as errors or failure. And this will be reflected in the final 'reports' too. If that CheckBox is ticked, at least from the reports, you will know that the failure is from that particular screen