使用jmeter-to-k6转换JMX至k6脚本时遇未识别元素错误

Hey there, let's break down and fix this error you're hitting when converting your JMeter JMX to a k6 script.

What's causing the failure? #

The kg.apc.jmeter.threads.UltimateThreadGroup is part of JMeter Plugins—a third-party extension for JMeter—not the core built-in components. The jmeter-to-k6 tool only supports native JMeter elements out of the box; it can't recognize or process third-party plugin components, which is why your conversion stops abruptly.

That Node.js DEP0018 warning? It's a separate, non-critical notice: it just means the tool uses an outdated way of handling Promise rejections, but it's not what's blocking your conversion. The real issue is the unsupported UltimateThreadGroup.

How to resolve this #

Here are two practical solutions based on your needs:

1. Swap UltimateThreadGroup for JMeter's native Thread Group (simplest fix)

If your test logic doesn't depend on the advanced scheduling features of UltimateThreadGroup, replace it with JMeter's standard Thread Group:

• Open your JMX file in JMeter
• Delete the UltimateThreadGroup from your test plan
• Add a native Thread Group (right-click Test Plan > Add > Threads (Users) > Thread Group)
• Configure it to match your original UltimateThreadGroup's load profile as closely as possible (set thread count, ramp-up time, duration, etc.)
• Save the modified JMX and re-run the conversion command:

  jmeter-to-k6 C:\Tests\modified-test.jmx -o k6
  

2. Manually replicate UltimateThreadGroup logic in k6 (for advanced scheduling)

If you rely on the UltimateThreadGroup's complex multi-stage scheduling, you'll need to recreate that behavior in k6 after converting the rest of your test:

• First, remove the UltimateThreadGroup from your JMX, then convert the remaining elements to k6 using jmeter-to-k6

• Use k6's scenarios feature to mirror the UltimateThreadGroup's load stages. For example, if your original setup had 3 stages:

  • Ramp up to 50 threads over 2 minutes
  • Hold 50 threads for 10 minutes
  • Ramp down to 0 threads over 1 minute

  You'd add this scenario to your k6 script:

  export const options = {
    scenarios: {
      ultimate_thread_group_simulation: {
        executor: 'ramping-vus',
        startVUs: 0,
        stages: [
          { duration: '2m', target: 50 }, // Ramp up to 50 VUs
          { duration: '10m', target: 50 }, // Hold 50 VUs
          { duration: '1m', target: 0 }, // Ramp down to 0
        ],
        gracefulStop: '30s',
      },
    },
  };
  

  Tweak the duration and target values to match your original UltimateThreadGroup configuration.

Bonus check #

Scan your JMX for other third-party JMeter Plugin elements (like custom listeners or samplers)—these will also break the conversion. Replace them with native JMeter elements where possible, or plan to manually build their functionality in k6 if needed.

内容的提问来源于stack exchange，提问作者Sandeepa