地址：https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/wiki/Advanced-Configuration

Selecting Tests To Run

Running All Tests
Specifying <testFilesIncluded>
Specifying <testFilesIncluded> Using Regex
Specifying <testFilesExcluded>
Specifying <testFilesExcluded> Using Regex
Specifying The <testFilesDirectory>

Running All Tests

To run all tests held in the ${project.base.directory}/src/test/jmeter you just need to run the phase you have assigned to the execution phase.

In the example below the execution phase has been set to verify:

+---+
<project>[...]<build><plugins><plugin><groupId>com.lazerycode.jmeter</groupId> <artifactId>jmeter-maven-plugin</artifactId> <version>2.0.3</version> <executions> <execution> <id>jmeter-tests</id> <goals> <goal>jmeter</goal> </goals> </execution> </executions> </plugin> </plugins> </build> [...] </project> +---+

So to run all the tests type:

mvn verify

Specifying <testFilesIncluded>

You can explicitly specify which tests in the ${project.base.directory}/src/test/jmeter should be run by using the <jMeterTestFiles> tag:

+---+
<project>[...]<build><plugins><plugin><groupId>com.lazerycode.jmeter</groupId> <artifactId>jmeter-maven-plugin</artifactId> <version>2.0.3</version> <executions> <execution> <id>jmeter-tests</id> <goals> <goal>jmeter</goal> </goals> </execution> </executions> <configuration> <testFilesIncluded> <jMeterTestFile>test1.jmx</jMeterTestFile> <jMeterTestFile>test2.jmx</jMeterTestFile> </testFilesIncluded> </configuration> </plugin> </plugins> </build> [...] </project> +---+

This time when you type mvn verify only test1.jmx and test2.jmx will be run.

Specifying <testFilesIncluded> Using Regex

You can also use a regex to specify which tests to include, below is a simple example showing how to include all tests starting with the text foo:

+---+
<project>[...]<build><plugins><plugin><groupId>com.lazerycode.jmeter</groupId> <artifactId>jmeter-maven-plugin</artifactId> <version>2.0.3</version> <executions> <execution> <id>jmeter-tests</id> <goals> <goal>jmeter</goal> </goals> </execution> </executions> <configuration> <testFilesIncluded> <jMeterTestFile>foo*.jmx</jMeterTestFile> </testFilesIncluded> </configuration> </plugin> </plugins> </build> [...] </project> +---+

Specifying <testFilesExcluded>

Rather than specifying which tests should be run, you could alternatively specify which tests in the ${project.base.directory}/src/test/jmeter you do not wish to run by using the <excludeJMeterTestFiles> tag:

+---+
<project>[...]<build><plugins><plugin><groupId>com.lazerycode.jmeter</groupId> <artifactId>jmeter-maven-plugin</artifactId> <version>2.0.3</version> <executions> <execution> <id>jmeter-tests</id> <goals> <goal>jmeter</goal> </goals> </execution> </executions> <configuration> <testFilesExcluded> <excludeJMeterTestFile>test3.jmx</excludeJMeterTestFile> <excludeJMeterTestFile>test4.jmx</excludeJMeterTestFile> </testFilesExcluded> </configuration> </plugin> </plugins> </build> [...] </project> +---+

This time when you type mvn verify all tests in the tests in the${project.base.directory}/src/test/jmeter apart from test3.jmx and test4.jmx will be run.

Specifying <testFilesExcluded> Using Regex

You can also use a regex to specify which tests to exclude, below is a simple example showing how to include all tests ending with the text bar:

+---+
<project>[...]
<build><plugins><plugin><groupId>com.lazerycode.jmeter</groupId> <artifactId>jmeter-maven-plugin</artifactId> <version>2.0.3</version> <executions> <execution> <id>jmeter-tests</id> <goals> <goal>jmeter</goal> </goals> </execution> </executions> <configuration> <testFilesExcluded> <excludeJMeterTestFile>*bar.jmx</excludeJMeterTestFile> </testFilesExcluded> </configuration> </plugin> </plugins> </build> [...] </project> +---+

Specifying The <testFilesDirectory>

You can specify the directory where the test files are located in your file system (by default the plugin will assume they are in ${project.base.directory}/src/test/jmeter)

+---+
<project>[...]<build><plugins><plugin><groupId>com.lazerycode.jmeter</groupId> <artifactId>jmeter-maven-plugin</artifactId> <version>2.0.3</version> <executions> <execution> <id>jmeter-tests</id> <goals> <goal>jmeter</goal> </goals> </execution> </executions> <configuration> <testFilesDirectory>/scratch/testfiles/</testFilesDirectory> </configuration> </plugin> </plugins> </build> [...]

转载于:https://www.cnblogs.com/ceshi2016/p/5986988.html

Jmeter-Maven-Plugin高级应用：Selecting Tests To Run相关推荐

解决Jetty Maven Plugin：Please initialize the log4j system properly(转)
解决Jetty Maven Plugin:Please initialize the log4j system properly. Jetty Maven Plugin环境: <plugin&g ...
Versions maven plugin 修改版本
文章目录版本控制修改全模块版本号修改模块版本修改指定模块版本号参数介绍代码经过长期修改后,版本号却从没有推进,导致个别release稳定版的模块更新代码之后,其他开发机器并不会自动更新本地 ...
eclipse Plugin execution not covered by lifecycle configuration：maven.***.plugin
具体是pom 不能引入和识别对应maven-plugin: 例如:Plugin execution not covered by lifecycle configuration: org.apache ...
org.springframework.boot:spring boot maven plugin丢失---SpringCloud Alibaba_若依微服务框架改造_--工作笔记012
警告]"build.plugins.plugin.version"for org.springframework.boot:spring boot maven plugin丢失. ...
Spring Boot的Maven插件Spring Boot Maven plugin详解
pring Boot的Maven插件(Spring Boot Maven plugin)能够以Maven的方式为应用提供Spring Boot的支持,即为Spring Boot应用提供了执行Maven ...
wro4j和maven plugin在编译期间压缩静态资源
优化前: 基本上所有的jsp都引用了这一大坨静态文件: <link rel="stylesheet" type="text/css" href=&quo ...
wro4j和maven plugin在编译期间压缩静态资源.
优化前: 基本上所有的jsp都引用了这一大坨静态文件: <link rel="stylesheet" type="text/css" href=" ...
no main manifest attribute maven package 运行打包后的jar包报错：xxx.jar中没有主清单属性通过配置 maven plugin 解决
文章目录命令行运行生成的jar包,报错解决手动修复修改打包规则一劳永逸 MANIFEST.MF demo Others IDEA 中关于 main class 的配置命令行运行生成的jar ...
eclipse maven plugin 插件安装和配置
本文转自:http://www.blogjava.net/fancydeepin/archive/2012/07/13/eclipse_maven3_plugin.html maven3 安装: 安装 ...

Jmeter-Maven-Plugin高级应用：Selecting Tests To Run