JMX Converter issue - java.lang.IllegalArgumentException: Problem loading XML from:'xxx\yyy\zzz\SDPUIPerformanceSuite.jmx'.

[Shashy1508]

Cause: CannotResolveClassException: com.googlecode.jmeter.plugins.webdriver.config.ChromeDriverConfig

Detail:com.thoughtworks.xstream.converters.ConversionException: ---- Debugging information ---- cause-exception : com.thoughtworks.xstream.converters.ConversionException cause-message : first-jmeter-class : org.apache.jmeter.save.converters.HashTreeConverter.unmarshal(HashTreeConverter.java:66) class : org.apache.jmeter.save.ScriptWrapper required-type : org.apache.jmeter.save.ScriptWrapper converter-type : org.apache.jmeter.save.ScriptWrapperConverter path : /jmeterTestPlan/hashTree/hashTree/hashTree[3]/com.googlecode.jmeter.plugins.webdriver.config.ChromeDriverConfig line number : 98 version : 1.21

I am trying to convert the jmx using the command "java -jar jmdsl.jar jmx2dsl SDPUIPerformanceSuite.jmx" I have plugins jar downloaded and placed in lib/ext in jmeter , it runs perfectly in jmeter GUI but while trying to convert the JMX to DSL using the above mentioned command get the said error.I understand this is an external plugin and am not able to understand what I need to do so this org.apache.jmeter.save.converters.HashTreeConverter.unmarshal(HashTreeConverter class can work with jmx2dsl jar .Pls provide necessary guidance in resolving this issue.

[rabelenda]

Hello, thank you for bringing this to attention!

Yes, it seems that you are using Selenium WebDriver plugin in your test plan, and the jmdsl.jar does not include such classes so it doesn't know how to convert them. If you add the required jars to the java command you should be able to convert the test plan (using test element wrappers).

Here we provide a solution for a similar scenario.

This should provide a funcional, but not optimal conversion. If you are interested on a more optimal conversion, maybe you can provide an example of the test plan you are trying to convert and we can discuss ideas on the expected conversion, and how jmx2dsl could convert them.

Regards

[Shashy1508]

Thanks , let me try this out

From: rabelenda @.> Sent: Monday, October 16, 2023 9:07 PM To: abstracta/jmeter-java-dsl @.> Cc: Javalekar, Satish D @.>; Author @.> Subject: [EXT] Re: [abstracta/jmeter-java-dsl] JMX Converter issue - java.lang.IllegalArgumentException: Problem loading XML from:'xxx\yyy\zzz\SDPUIPerformanceSuite.jmx'. (Issue #230)

[Actual Sender is @.**@.>]

Hello, thank you for bringing this to attention!

Yes, it seems that you are using Selenium WebDriver plugin in your test plan, and the jmdsl.jar does not include such classes so it doesn't know how to convert them. If you add the required jars to the java command you should be able to convert the test plan (using test element wrappers).

Herehttps://github.com/abstracta/jmeter-java-dsl/issues/191#issuecomment-1594744526 we provide a solution for a similar scenario.

This should provide a funcional, but not optimal conversion. If you are interested on a more optimal conversion, maybe you can provide an example of the test plan you are trying to convert and we can discuss ideas on the expected conversion, and how jmx2dsl could convert them.

Regards

— Reply to this email directly, view it on GitHubhttps://github.com/abstracta/jmeter-java-dsl/issues/230#issuecomment-1764758894, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BDG3QQTOB4RHTVSBQLELI7LX7VIC7AVCNFSM6AAAAAA55HJWJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRUG42TQOBZGQ. You are receiving this because you authored the thread.Message ID: @.**@.>> Confidentiality Notice: This electronic message transmission, including any attachment(s), may contain confidential, proprietary, or privileged information from ACS International Ltd., ("ACS-I"), a wholly-owned subsidiary of the American Chemical Society ("ACS"). If you have received this transmission in error, be advised that any disclosure, copying, distribution, or use of the contents of this information is strictly prohibited. Please destroy all copies of the message and contact the sender immediately by either replying to this message or calling 614-447-3600.