Skip to content

Dated version for Karate Gatling integration #2677

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
vlad-i-ionita opened this issue Mar 27, 2025 · 5 comments
Open

Dated version for Karate Gatling integration #2677

vlad-i-ionita opened this issue Mar 27, 2025 · 5 comments

Comments

@vlad-i-ionita
Copy link

I am trying to integrate Gatling inside a framework that uses Karate and am using the 1.5.1 version of karate core as part of an enterprise level organization

It uses version 3.9.5 of Gatling and we would want a more recent version to be used as this reflects inside the index.html reports, making it visible to customer stakeholders, hence it represents an important aspect in our delivery workflow

Image

Thank you in advance for your assistance

@CPogX
Copy link
Contributor

CPogX commented Mar 31, 2025

How do you feel about 3.11? It will remove the message. I don't want to upgrade to 3.13 because it prevents combining multiple log files into 1 report. Additionally it removes akka and requires jvm args so there's work to consuming the upgrade for current users. 3.11.5 to consume would be just as as simple as upgrading the karate version, and the maven/gradle plugin version if they are using it. Let me know what you think.

@vlad-i-ionita
Copy link
Author

Hello and thank you for the quick response!

Yes. We are definitely fine with 3.11 as long as it removes the message

Furthermore, I saw in the following thread: #762
a gatling limitation with not interpreting properly the results within the subgroups upon executing the karate tests with it

Image

Will upgrading to 3.11 solve this particular issue as well?

Thank you once again for your input. I appreciate the support

@CPogX
Copy link
Contributor

CPogX commented Apr 1, 2025

I have no idea if it will have an impact. Are you experiencing this issue yourself? I don't really understand the scenario, so my initial reaction is sort of "just don't do it that way", but I don't understand. I've never had any issues like this in my experience, but if you are experiencing it and can explain I can see if I have any insight.

@vlad-i-ionita
Copy link
Author

No worries. I will check out the upgraded version its results. If the issue still persists, I will detail it in a separate ticket
Can you please inform me about the steps I need to take in order to make the upgrade? I saw that a PR was opened and it's waiting to be merged

@CPogX
Copy link
Contributor

CPogX commented Apr 3, 2025

Ya, so @ptrthomas needs to review, and if he is okay with it then would approve/merge it to the develop branch, and then would include it in a release. I can't give you a concrete timeline on that.

If you want to see immediately, you could clone my branch and build the jar on your local.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants