Versions Compared

Old Version 3

changes.mady.by.user ASF Infrabot

Saved on

compared with

New Version Current

changes.mady.by.user ASF Infrabot

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: converted to 1.6 markup

The JMeter Jmx Test Plan Format TableOfContents

Table of Contents

JMX Format

Wiki MarkupJMX are save using \[http://xstream.codehaus.org/ xtream\].

Differences between 2.0 and 2.1 Format

...

upgrade.properties was used purely to allow class name changes. renamed elements mapping can also be found in upgrade.properties.

Jmx Test Plan 2.1 Format

TODOMapping between node name (example: <hashTree> or <TestPlan>) and the real package.classname is done using saveservice.properties.

2.1 Format Example

Here's what a 2.1 jmx format would look like:

No Format
<jmeterTestPlan version="1.2" properties="1.8">
  <hashTree>
    <TestPlan guiclass="TestPlanGui" testclass="TestPlan" testname="Test Plan" enabled="true">
    ...
    </TestPlan>
    <hashTree>
      <ThreadGroup guiclass="ThreadGroupGui" testclass="ThreadGroup" testname="Thread Group" enabled="true">
      ...
      </ThreadGroup>
      <hashTree>
        <RecordingController guiclass="RecordController" testclass="RecordingController" testname="Recording Controller" enabled="true"/>
        <hashTree>
          <HTTPSampler guiclass="HttpTestSampleGui" testclass="HTTPSampler" testname="/my_webapp/root/page" enabled="true">
          ...
          </HTTPSampler>
          <hashTree>
            <HeaderManager guiclass="HeaderPanel" testclass="HeaderManager" testname="Browser-derived headers" enabled="true">
            ...
            </HeaderManager>
            ...
            <hashTree/>
          </hashTree>
      <hashTree/>
    </hashTree>
  </hashTree>

Jmx Test Plan 2.0 Format

...

How to save in 2.0 Format

Wiki MarkupSet properties in jmeter.properties. See \[:JMeterFAQ:JMeter FAQ\].

2.0 Format Example

Here's what a 2.0 jmx format would look like:

...