TeamCity results don't match JMeter's

Question

I\'m currently using JMeter to load test some application, I used the duration assertion and I set it to, let\'s say 200, when the load time exceeds 200, the Request in the Resu

Answer 1

Take a look at the Performance Metrics Calculation under Build Features in Team City's project. You need to make sure that assertions is checked in order to make the build fail on assertions.

In addition to that, the newer versions of JMeter and Team City add more columns to the .jtl file that is output, so you need to make sure your "success" column is in the 5th spot in the file. I found this out after coming across this post in the TeamCity JMeter Plugin git repo: https://github.com/jtorgan/jmeter_plugin/issues/24#issuecomment-421016226

Instead of creating a script, I just made sure to remove some columns in the JMeter user.properties settings on the TeamCity server to make sure the success column was in the 5th spot.

Here were the columns I had to turn off under user.properties for JMeter:

jmeter.save.saveservice.response_message=false
jmeter.save.saveservice.thread_name=false
jmeter.save.saveservice.data_type=false