![]() ![]() So this needed to be reflected in the APDEX computation.Īnother improvement on report is the reorganization of Statistics table: This feature was really needed because those 2 thresholds always vary depending on type of transaction concerned, for example, for an e-commerce website, a user will accept to wait more during a payment transaction than when doing a search. With this version, in the APDEX table, you’ll be able to customize per transaction the values of: This new feature introduced in version 3.0 continues to improve in Apache JMeter 3.2. It also allows you to send annotations to Graphite which gives you nice graphs with custom meta-data to better describe your load test Implementation uses Influx DB HTTP API which simplifies InfluxDB configuration as you don’t need to configure Graphite Connector anymore.Implementation uses Asynchronous HTTP Client API which makes it more efficient. ![]() This improves existing feature in 2 ways: In Apache JMeter 3.2, the Backend Listener has been enhanced with a new Backend Listener client that allows writing results into an InfluxDB Backend. Report / Dashboard improvements: Live Reporting in Influx DB: This both simplifies configuration for JMeter users and eases maintainability of the project by reducing code base and dropping another deprecated library.įinally, Sonar Qube has been setup for Apache JMeter build process and an important work on code quality and test coverage has been done, you can see the Sonar JMeter report. In another field, the old commons-httpclient library has been dropped as Preemptive Basic Authentication has been implemented for HTTPClient4. Now configuration of Logging is done in log4j2.xml file located in jmeter/bin folder. This migration allowed the drop of 4 outdated libraries. This will also improve logging performances as it relies on one of the fastest logging frameworks ( Apache Log4j2 benchmark). Thanks to the contribution of Woonsan Ko, logging has been migrated from LogKit to SLF4J and Apache Log4j2 bringing standard and easier configuration of logging as it now relies on 2 major logging frameworks. Core improvements:Īpache JMeter 3.2 is also a major version as migration to Java 8 has been done with a tons of code improvements taking advantage of Java 8 great features (Lambdas, Streams, …). This feature will be enhanced in future versions of JMeter. Http Request element: Replacement in Arguments, Path and HostĪlso note that search feature give you now the number of matches for the search.In HeaderManager element: Replacement in header values.It is important to know that “ReplaceAll” is a first shot, and for now does not do replacement on all elements, it does it on most frequent use cases when correlating: HTTP(S) Test Script Recorder Filtering Search / Replace featureĪ new feature that’s very useful for correlation has been introduced which allows replacing some data by variables for example. Simplified HTTP Request UI:įirst one for most common properties and particularly the “Prefix” which allows you to name each transaction during recording. The UI of JMeter which is often criticized for its complexity has been simplified in many fields. We’ll see in this blog what features have been brought by Apache JMeter team and the 20 contributors who helped creating this awesome new version. ![]() With 55 enhancements and 41 bug fixes, it is a major version that deserves your attention, and of course upgrading is highly advised. Apache JMeter 3.2 in few numbers:Īlthough there is some confusion in the community on JMeter version numbering, version 3.2 is not a minor version. We’ll show you in this blog the most important ones. 4 months after the 3.1 release, Apache JMeter 3.2 has been released with another set of very nice features. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |