Modifying Properties

Pages 12

Modifying Properties

Using Your Own Properties Files

The easiest way to configure JMeter with this plugin is to supply your own properties files. When it starts up the plugin will scan the ${project.base.directory}/src/test/jmeter directory for the following files:

jmeter.properties
saveservice.properties
upgrade.properties
system.properties
user.properties
global.properties

Adding Additional Properties To <propertiesJMeter>

It is possible to set properties that configure the main JMeter library. To set those properties you will need to specify each property in your pom.xml in the config element <propertiesJmeter>(The example below shows a property called log_level.jmeter being set).

Each property specified is merged into the JMeter properties file jmeter.properties, it will overwrite any identical properties within the file.

+---+

<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>

                        <propertiesJMeter>

                            <log_level.jmeter>DEBUG</log_level.jmeter>

                        </propertiesJMeter>

                    </configuration>

                </plugin>

            </plugins>

        </build>

    [...]

</project>

+---+

Adding Additional Properties To <propertiesSaveService>

It is possible to set properties that configure the Saveservice of the main JMeter library. To set those properties you will need to specify each property in your pom.xml in the config element<propertiesSaveservice> (The example below shows a property called HTTPSampler2 being set).

Each property specified is merged into the JMeter properties file saveservice.properties, it will overwrite any identical properties within the file.

+---+

<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>

                        <propertiesSaveService>

                            <HTTPSampler2>org.apache.jmeter.protocol.http.sampler.HTTPSampler2</HTTPSampler2>

                        </propertiesSaveService>

                    </configuration>

                </plugin>

            </plugins>

        </build>

    [...]

</project>

+---+

Adding Additional Properties To <propertiesUpgrade>

It is possible to set properties that are used in the oldValue to newValue upgrade mapping of the main JMeter library. To set those properties you will need to specify each property in yourpom.xml in the config element <propertiesUpgrade>. (The example below shows a property called my.old.ClassName being set).

Each property specified is merged into the JMeter properties file upgrade.properties, it will overwrite any identical properties within the file.

+---+

<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>

                        <propertiesUpgrade>

                            <my.old.ClassName>my.new.ClassName</my.old.ClassName>

                        </propertiesUpgrade>

                    </configuration>

                </plugin>

            </plugins>

        </build>

    [...]

</project>

+---+

Adding Additional Properties To <propertiesUser>

JMeter user properties are properties supplied to JMeter that can be used in JMeter tests. To set user properties you will need to specify each property in your pom.xml in the config element<propertiesUser> (The example below shows a property called threads and a propery calledtestIterations being set).

Each property specified is merged into the JMeter properties file user.properties, it will overwrite any identical properties within the file.

+---+

<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>

                        <propertiesUser>

                            <threads>10</threads>

                            <testIterations>5</testIterations>

                        </propertiesUser>

                    </configuration>

                </plugin>

            </plugins>

        </build>

    [...]

</project>

+---+

Adding Additional Properties To <propertiesGlobal>

Global properties are properties that are sent to the remote machines. To set those properties you will need to specify each property in your pom.xml in the config element<propertiesGlobal> (The example below shows a property called threads and a property calledtestIterations being set).

Each property specified is merged into the JMeter properties file global.properties, it will overwrite any identical properties within the file.

+---+

<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>

                        <propertiesGlobal>

                            <threads>10</threads>

                            <testIterations>5</testIterations>

                        </propertiesGlobal>

                    </configuration>

                </plugin>

            </plugins>

        </build>

    [...]

</project>

+---+

Adding Additional Properties To <propertiesSystem>

JMeter can set system properties, these are global environment properties accessible by all applications running in the same JVM (They are not accessible outside the JVM). To set system properties you will need to specify each property in your pom.xml in the config element<propertiesSystem> (The example below shows a property called my.system.property being set).

Each property specified is merged into the JMeter properties file system.properties, it will overwrite any identical properties within the file.

+---+

<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>

                        <propertiesSystem>

                            <my.system.property>my.system.property.value</my.system.property>

                        </propertiesSystem>

                    </configuration>

                </plugin>

            </plugins>

        </build>

    [...]

</project>

+---+

Setting <propertiesReplacedByCustomFiles>

By default all properties specified in the settings above will be merged with any existing properties. If you want them to be replaced instead you can do this by setting<propertiesReplacedByCustomFiles> to true (it is false by default). Please think very carefullybefore doing this, the reason we merge properties by default is to ensure that all properties are merged into the latest valid versions of the properties files supplied with JMeter. If you overwrite the properties files but are missing a property that is required by JMeter things will most likely break.

+---+

<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>

                        <propertiesReplacedByCustomFiles>${basedir}true</propertiesReplacedByCustomFiles>

                    </configuration>

                </plugin>

            </plugins>

        </build>

    [...]

</project>

+---+

Specifying A <customPropertiesFile>

This will allow you to set an absolute path to JMeter custom (test dependent) properties file. This is the equivalent of setting " --addprop my.properties" on the command line.

+---+

<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>

                        <customPropertiesFiles>

                            <file>/user/home/myuser/myCustom.properties</file>

                        </customPropertiesFiles>

                    </configuration>

                </plugin>

            </plugins>

        </build>

    [...]

</project>

+---+

Specifying The <propertiesFilesDirectory>

You can specify the directory where the .properties 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>

                        <propertiesFilesDirectory>/user/home/myuser/properties</propertiesFilesDirectory>

                    </configuration>

                </plugin>

            </plugins>

        </build>

    [...]

</project>

+---+

Jmeter-Maven-Plugin高级应用：Modifying Properties的更多相关文章

Spring Boot的Maven插件Spring Boot Maven plugin详解
Spring Boot的Maven插件(Spring Boot Maven plugin)能够以Maven的方式为应用提供Spring Boot的支持,即为Spring Boot应用提供了执行Mave ...
基于Jmeter+maven+Jenkins构建性能自动化测试平台
一.目的: 为能够将相关系统性能测试做为常规化测试任务执行,且可自动无人值守定时执行并输出性能测试结果报告及统计数据,因此基于Jmeter+maven+Jenkins构建了一套性能自动化测试平台 ...
Jmeter+maven+Jenkins构建云性能测试平台（mark 推荐）
转自:http://www.cnblogs.com/victorcai0922/archive/2012/06/20/2555502.html Jmeter+maven+Jenkins构建云性能测试平 ...
学习Maven之Cobertura Maven Plugin
cobertura-maven-plugin是个什么鬼? cobertura-maven-plugin是一个校验单元测试用例覆盖率的工具,可以生成一个测试覆盖率报告,可以给单元测试用例编写提供参考. ...
Maven实现Web应用集成測试自己主动化 -- 部署自己主动化(WebTest Maven Plugin)
上篇:Maven实现Web应用集成測试自己主动化 -- 測试自己主动化(WebTest Maven Plugin) 之前介绍了怎样在maven中使用webtest插件实现web的集成測试,这里有个遗留 ...
解决Jetty Maven Plugin：Please initialize the log4j system properly(转)
解决Jetty Maven Plugin:Please initialize the log4j system properly.Jetty Maven Plugin环境: <plugin> ...
Spring Boot Maven Plugin（一）：repackage目标
简介 Spring Boot Maven Plugin插件提供spring boot在maven中的支持.允许你打包可运行的jar包或war包. 插件提供了几个maven目标和Spring Boot ...
Spring Boot Maven Plugin打包异常及三种解决方法：Unable to find main class
[背景]spring-boot项目,打包成可执行jar,项目内有两个带有main方法的类并且都使用了@SpringBootApplication注解(或者另一种情形:你有两个main方法并且所在类都没 ...
Maven实现Web应用集成測试自己主动化 -- 測试自己主动化(WebTest Maven Plugin)
近期在appfuse看到使用webtest-maven-plugin实现Web应用的集成測试,研究了下.感觉很不错.对于Web应用自己主动构建很有帮助,在性能測试之前能够保证Web应用的基本功能工作正 ...

随机推荐

[BZOJ4487][JSOI2015]染色问题(容斥)
一开始写了7个DP方程,然后意识到这种DP应该都会有一个通式. 三个条件:有色行数为n,有色列数为m,颜色数p,三维容斥原理仍然成立. 于是就是求:$\sum_{i=0}^{n}\sum_{j=0}^ ...
【二分】【动态规划】Gym - 101156E - Longest Increasing Subsequences
求最长上升子序列方案数. 转载自:http://blog.csdn.net/u013445530/article/details/47958617,如造成不便,请博主联系我. 数组A包含N个整数(可能 ...
hdu 5301 Buildings (2015多校第二场第2题) 简单模拟
题目链接:http://acm.hdu.edu.cn/showproblem.php?pid=5301 题意:给你一个n*m的矩形,可以分成n*m个1*1的小矩形,再给你一个坐标(x,y),表示黑格子 ...
bzoj1477 poj1061 青蛙的约会
Description 两只青蛙在网上相识了,它们聊得很开心,于是觉得很有必要见一面.它们很高兴地发现它们住在同一条纬度线上,于是它们约定各自朝西跳,直到碰面为止.可是它们出发之前忘记了一件很重要的事 ...
Hibernate与MyBatis的对比总结
最近做了一个Hibernate与MyBatis的对比总结,希望大家指出不对之处. 第一章 Hibernate与MyBatis Hibernate 是当前最流行的O/R mapping框架,它出 ...
Android实现两次按下返回键退出
@Override public boolean onKeyDown(int keyCode, KeyEvent event) { if(keyCode == KeyEvent.KEYCODE_BAC ...
写给在Java和.net中徘徊的新手
在很多网站上,网友都会问一个相同的问题,到底是学Java还是.net,个有个的见解. 自从.Net问世以来,程序员都很关心的一个问题是「该学Java或.NET」.我也在挣扎,该「该继续Java的研究, ...
MVC使用Gantt Chart实现甘特图,管理事情进度
借助"甘特图",可以直观地了解任务.活动.工作的进度.dhtmlxGantt是一个开源的Javacirpt库,能帮助我们快速创建"甘特图",本篇体验在MVC中的 ...
【转载】C#堆和栈的区别
原文出处理解堆与栈对于理解.NET中的内存管理.垃圾回收.错误和异常.调试与日志有很大的帮助.垃圾回收的机制使程序员从复杂的内存管理中解脱出来,虽然绝大多数的C#程序并不需要程序员手动管理内存,但这 ...
Java 内存释放
 问题一什么叫垃圾回收机制 垃圾回收是一种动态存储管理技术它自动地释放不再被程序引用的对象按照特定的垃圾收集算法来实现资源自动回收的功能.当一个对象不再被引用的时候内存回收它占领的空间 ...

Jmeter-Maven-Plugin高级应用：Modifying Properties

Modifying Properties

Pages 12