Skip to content

fix: jmeter-script-gen template — intProp var refs + saveConfig cross-version breakage#173

Closed
Wool-xing wants to merge 1 commit into
mainfrom
fix/jmeter-script-gen-compat
Closed

fix: jmeter-script-gen template — intProp var refs + saveConfig cross-version breakage#173
Wool-xing wants to merge 1 commit into
mainfrom
fix/jmeter-script-gen-compat

Conversation

@Wool-xing
Copy link
Copy Markdown
Owner

Summary

  • Fix <intProp>/<longProp> containing ${THREADS}/${RAMPUP}/${DURATION} variable refs → <stringProp>
  • Remove hardcoded <objProp name="saveConfig"> from ResultCollector (26 fields, delegates to jmeter.properties defaults)
  • Add JMeter version compatibility banner (JMeter 5.0 ~ 5.6.3)

Root cause

skills/jmeter-script-gen.md template used by automation-engineer agent to generate JMX files had two JMeter XML incompatibilities:

  1. Typed props (intProp/longProp) containing ${VAR} refs cause NumberFormatException at JMX load time (JMeter calls Integer.parseInt() on XML deserialization, before runtime variable substitution)
  2. Hardcoded SampleSaveConfiguration fields (e.g. responseMessage renamed to message in JMeter 5.5+) cause MissingFieldException across versions

Test plan

  • JMX loads without NumberFormatException in JMeter 5.6.3
  • JMX loads without MissingFieldException in JMeter 5.6.3
  • Verify JTL output contains expected fields via jmeter.properties defaults
  • Smoke test with jmeter -n -t api_load_test.jmx -l test.jtl

…-version breakage

Two bugs fixed:
1. ThreadGroup <intProp>/<longProp> containing ${THREADS}/${RAMPUP}/${DURATION}
   → changed to <stringProp> (JMeter runtime eval, not XML parse time)
2. Removed hardcoded <objProp name="saveConfig"> from ResultCollector
   → delegates to jmeter.properties defaults, compatible with JMeter 5.0~5.6.3

Added version compatibility banner documenting both constraints.
@Wool-xing Wool-xing closed this Jun 1, 2026
@Wool-xing Wool-xing deleted the fix/jmeter-script-gen-compat branch June 1, 2026 19:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant