Skip to content
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

Add an option to filter results after execution #238

Open
smithbr opened this Issue Sep 20, 2017 · 3 comments

Comments

3 participants
@smithbr
Copy link

smithbr commented Sep 20, 2017

I want to use something like the Filter Results Tool to filter out samplers I don't want in my result set.

My tests are run from Jenkins using the Performance Plugin with some pass/fail criteria (e.g. "Fail this build if response times degrade > 10% from the previous build").

My BeanShell and other setup-type samplers keep failing this criteria because their timings are so small. Just going from 5 -> 6 milliseconds for some tiny BeanShell sampler is enough to fail the Performance Plugin criteria.

Therefore I want to filter those out after the test has completed, preferably using the existing plugin.

https://jmeter-plugins.org/wiki/FilterResultsTool/
https://mvnrepository.com/artifact/kg.apc/jmeter-plugins-filterresults

@Ardesco

This comment has been minimized.

Copy link
Contributor

Ardesco commented Sep 20, 2017

I'm guessing you want this:

https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/wiki/Adding-additional-libraries-to-the-classpath

Stuff from the jmeter-plugins team has previously had transitive dependency issues though, have a look here for more info:

https://stackoverflow.com/questions/42268380/how-to-use-perfmon-plugins-with-jmeter-maven-plugin/42345443#42345443

@smithbr

This comment has been minimized.

Copy link
Author

smithbr commented Sep 21, 2017

Even with adding jpgc-filterresults as a dependency, the problem is that the plugin only works by manually running it after the execution, like jmeter/bin/FilterResults.sh --input-file ... which (I think?) requires a local install of jmeter, setup with this plugin, installed on the machine. So you kind of can't do anything with it using the jmeter-maven-plugin.

Take a look here for the usage I'm talking about... I don't think there's way to do this currently during my maven test, right? https://jmeter-plugins.org/wiki/FilterResultsTool/

@pmouawad pmouawad added this to the 2.8.0 milestone Feb 11, 2018

@pmouawad pmouawad added this to High priority in ISSUE TRACKING Aug 3, 2018

@pmouawad pmouawad modified the milestones: 2.8.0, 2.9.0 Oct 4, 2018

@pmouawad pmouawad modified the milestones: 2.8.1, 2.8.2 Nov 11, 2018

@pmouawad pmouawad modified the milestones: 2.8.2, 2.8.3 Dec 27, 2018

@pmouawad pmouawad modified the milestones: 2.8.3, 2.8.4 Jan 15, 2019

@pmouawad pmouawad modified the milestones: 2.8.4, 2.8.5 Jan 29, 2019

@pmouawad pmouawad modified the milestones: 2.8.6, 2.8.7 Feb 19, 2019

@Ardesco

This comment has been minimized.

Copy link
Contributor

Ardesco commented Mar 10, 2019

Sounds like a job for the maven exec plugin (http://mojo.codehaus.org/exec-maven-plugin/).

You can set it up to run in the post-integration-test phase and then run ${project.build.directory}/jmeter/bin/FilterResults.sh --input-file... using that plugin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.