gatling-parser | Excel parseable report from Gatling simulation log file

by henri-tremblay Java Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions Vulnerabilities Install Support

kandi X-RAY | gatling-parser Summary

gatling-parser is a Java library. gatling-parser has no vulnerabilities, it has build file available and it has low support. However gatling-parser has 2 bugs. You can download it from GitHub.

Generates an Excel parseable report from Gatling simulation log file for all server calls and presenting the usual metrics. You can lauch it from the command line using parse.bat which calls mvn exec:java. The result is a file called simulation-result.txt which contains one line per request in the usual Gatling details section. The columns are the same (name, execution, min, max, mean, stdDeviation, percentile95, percentile99) and separated by a tabulation. You can easily load it in Excel and play with it is easy. This report is really useful since Gatling doesn’t provide, yet, a single view of the performance of every requests. The last simulation.log format tested was version 2.2.2. Please, let me know in case of issues with a newer version.

Support

Quality

Security

License

Reuse

Support

gatling-parser has a low active ecosystem.

It has 9 star(s) with 3 fork(s). There are 7 watchers for this library.

It had no major release in the last 6 months.

There are 1 open issues and 2 have been closed. On average issues are closed in 84 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of gatling-parser is current.

Quality

gatling-parser has 2 bugs (0 blocker, 0 critical, 0 major, 2 minor) and 10 code smells.

Security

gatling-parser has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

gatling-parser code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

gatling-parser does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

gatling-parser releases are not available. You will need to build from source code and install.

Build file is available. You can build the component from source.

gatling-parser saves you 108 person hours of effort in developing the same functionality from scratch.

It has 274 lines of code, 12 functions and 3 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed gatling-parser and discovered the below as its top functions. This is intended to give you an instant insight into gatling-parser implemented functionality, and help decide if they suit your requirements.

Command - line entry point
Calculates statistics for each request
Deduces the output filename

Get all kandi verified functions for this library.

gatling-parser Key Features

No Key Features are available at this moment for gatling-parser.

gatling-parser Examples and Code Snippets

No Code Snippets are available at this moment for gatling-parser.

Community Discussions

No Community Discussions are available at this moment for gatling-parser.Refer to stack overflow page for discussions.

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install gatling-parser

You can download it from GitHub.
You can use gatling-parser like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the gatling-parser component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: