You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
running jmx via mvn clean verify "-DjMeterTestFile=$JMX_FILE" command
Explain clearly the reproducer:
What should happen (OK Case) : All requests (read,update,delete ones from jmx should pass)
What happens (KO Case): deleet requests from jmx are failing
on further debugging, we are getting 400 bad request fro Delete requests . URL of delete requests are not getting formed properly.
eg : cpm/business/v1/deleteContract/customer//contract/ .no value between customer and contract. ${provider_customer_id} is null.
please suggest fix on how to handle this.
The text was updated successfully, but these errors were encountered:
This doesn't look like it's anything to do with the plugin, it's correctly running the .jmx file. Your issues looks to be something you have set in your test plan.
My best guess would be that your JSON path expression to extract the provider_customer_id ($.resources[0].id) is incorrect, or that response from the server you are testing is not working properly.
Either way this is nothing to do with the maven plugin.
Thank you for your reply. However same jmx is working via jmeter UI but not with maven jmeter plugin(delete requests are not working). Could you suggest any possible reason for this behavior?
When reporting an issue:
java version "1.8.0_231", Apache Maven 3.6.0 , jmeter maven plugin 3.0.0 (also tried 3.6.0, 3.7.0)
pom provided:
pom.xml.tar.gz
JMX provided:
Stability_21.1_TrafficModel_01232021_10aug21.jmx.tar.gz
running jmx via mvn clean verify "-DjMeterTestFile=$JMX_FILE" command
on further debugging, we are getting 400 bad request fro Delete requests . URL of delete requests are not getting formed properly.
eg : cpm/business/v1/deleteContract/customer//contract/ .no value between customer and contract. ${provider_customer_id} is null.
please suggest fix on how to handle this.
The text was updated successfully, but these errors were encountered: