https://bz.apache.org/bugzilla/show_bug.cgi?id=63101

            Bug ID: 63101
           Summary: Propose a menu item to generate readable overview of
                    Test Plan
           Product: JMeter
           Version: 5.0
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Main
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: JMETER_5.1

As per discussion on mailing list:

http://mail-archives.apache.org/mod_mbox/jmeter-dev/201901.mbox/%3CCAH9fUpZEBMpR4oiBL54%2BTk1Hm%3DnSLm2uZas50k5xqKpw8knB%2Bg%40mail.gmail.com%3E

There is a need in JMeter since we're not a DSL based tool, to provide an
overview of the test for documentation purpose.
It would also help a lot on issue reporting for example.

Currently, the only available option is to use schematic.sh which is:

- outdated (does not consider HttpSamplerProxy)
- very limited (Display element ClassName)
- not friendly to use, you need to copy the test plan in extras folder to make
it work

As the expected overview might depend a lot on what somebody wants to see, what
do you think of this as a first step:

- Create in new Tools menu Item (where we would move Curl, Export Transactions
for Report, Create Heap/Thread dump) an entry "Export as schematic overview"
- The feature would :
 open A dialog with Option path to enter Exporter

I see at least 2 ways to implement exporter:
        XSL with schematic way:
            + : Not much work
            - : XSL is not very readable nor friendly
            - : JMeter has no contract on XML

    Add an interface, JMeter would discover implementation and propose it:
        We would use the Visitor pattern 
        + : Very flexible
        + : Easier to maintain, we rely on Java Contract
        - : More work for user
    Note we can implement XSL Exporter as first step

    In the long term, maybe we could be proposing an exporter to YAML or JSON

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to