Skip to content

Releases: vdaburon/har-convertor-jmeter-plugin

Version 5.1 compatible with har generated by browsermob-proxy

17 May 14:35
Compare
Choose a tag to compare

Version 5.1, compatible with har generated by browsermob-proxy tool and csv file contains transaction infos. Use library har-to-jmeter-convertor 5.1.

Version 5.0 add external csv file and compatible with LoadRunner Web Recorder

10 May 08:34
Compare
Choose a tag to compare

Version 5.0, Add an external csv file with transaction information for JMeter Transaction Controller Name.
Add compatibility with HAR generated with LoadRunner Web Recorder Chrome Extension.

Version 3.2 date 2024-03-30 correct somes bugs

30 Mar 14:24
Compare
Choose a tag to compare

Version 3.2, Use library har-to-jmeter-convertor-2.3.jar, this version :

  • encode value for x-www-form-urlencoded when value contains space ' ' or equal '=' or slash '/' or plus '+' characters.
  • Correct add the content for body data for POST, PUT or PATCH if not x-www-form-urlencoded in the Record.xml file.

Version 3.1 date 2024-03-30 correct somes bugs

30 Mar 11:33
Compare
Choose a tag to compare

Version 3.1 date 2024-03-30, use library har-to-jmeter-convertor-2.2.jar, this library :

  • remove the header 'Content-length' because the length is computed by JMeter when the request is created.
  • POST or PUT could have query string and body with content so add query string to the path.
  • Set Content Encoding to UFT-8 for POST or PUT method and request Content-Type : application/json.
  • Add body data content in record.xml for PUT and PATCH methods.

Version 3.0

18 Mar 11:13
Compare
Choose a tag to compare

Version 3.0, add button "CONVERT AND LOAD GENERATED SCRIPT". File Chooser select only file and not directory.

Version 2.0

13 Mar 09:28
Compare
Choose a tag to compare

Add parameters page_start_number and sampler_start_number to facilitate partial recording of website navigation.

Modify for POST multipart/form-data don't put the content of the file in the Record.xml file because binary content could be large and not XML compatible.

Version 1.0 First Release

11 Mar 17:05
Compare
Choose a tag to compare

Version 1.0 First Release