-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Tags Do Not Work Correctly in karate-gatling:1.1.0 And Higher #1794
Comments
Issue #1794 - Fix for tags not being honored in karate-gatling
Thanks for accepting the PR. Can this issue be closed? |
@packleader the process we follow is that we keep this open with a just so you know, we are not planning an RC release until hacktoberfest gets over :| hope that's ok |
I have confirmed that this is fixed in |
@packleader thanks - if possible, can you also see if migration to gatling latest is straightforward, in which case we can do that too: https://gatling.io/docs/gatling/reference/current/upgrading/3.6-to-3.7/ |
I reviewed the release notes for Gatling 3.7, and I don't think any of the changes will impact us. Specifically, we don't seem to be using any of the newly-deprecated methods. I upgraded to 3.7.3 in the |
@packleader I upgraded to 3.7.3 and the gatling maven plugin to 4.0.1. as you said it all looked ok. but couldn't get the |
1.2.0 released |
In
karate-gatling
version1.1.0
and higher,karateFeature("classpath:mock/cats-delete.feature@name=delete")
works correctly, butkarateFeature("classpath:mock/cats-delete.feature", "@name=delete")
does not. It appears that thetags
var-args parameter is not being honored.Symptoms
Given:
karateFeature("classpath:mock/cats-delete.feature", "@name=delete")
Expected: Only the scenarios that match
@name=delete
incats-delete.feature
are executedActual: All scenarios in
cats-delete.feature
are executedTesting
The easiest way to repeat this bug is to modify line 27 of CatsSimulation.scala
Run the tests for
karate-gatling
and inspect the output for the following line. This confirms that all scenarios were executed, even those without@name=delete
.Fix
I think I have an idea of what's causing this, so I can investigate and submit a PR.
The text was updated successfully, but these errors were encountered: