jmeter-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 60675] New: TestFragment reference not well updated or no more accurate after renaming the Test Plan name
Date Wed, 01 Feb 2017 15:52:25 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=60675

            Bug ID: 60675
           Summary: TestFragment reference not well updated or no more
                    accurate after renaming the Test Plan name
           Product: JMeter
           Version: 3.1
          Hardware: PC
                OS: other
            Status: NEW
          Severity: critical
          Priority: P2
         Component: Main
          Assignee: issues@jmeter.apache.org
          Reporter: vherilier@gmail.com
  Target Milestone: ---

Created attachment 34699
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=34699&action=edit
Simple TestFragment/ModuleController scenario to reproduce the related issue

Hi,

Some JMeter users, I work with, encourters some TestFragment reference issues:
JMeter fails saying that: 

2017/01/31 15:03:18 INFO  - jmeter.save.SaveService: Loading file:
/home/ocadmin/IHSS/trunk/HSSTest/dist/usecases/Functional/Sh/Functional_Sh_DIT_UDR_IFC.jmx
2017/01/31 15:03:19 ERROR - jmeter.JMeter: Error in NonGUIDriver
org.apache.jorphan.util.JMeterStopTestException: ModuleController:[MC]
Reset-Msgs-Params has no selected Controller (did you rename some element in
the path to target controller?), test was shutdown as a consequence
        at
org.apache.jmeter.control.ModuleController.resolveReplacementSubTree(ModuleController.java:142)
        at org.apache.jmeter.JMeter.runNonGui(JMeter.java:905)
        at org.apache.jmeter.JMeter.startNonGui(JMeter.java:879)
        at org.apache.jmeter.JMeter.start(JMeter.java:504)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.apache.jmeter.NewDriver.main(NewDriver.java:259)

After investigations, it seems that since JMeter 3.1, the ModuleController
takes in account stronglier than previously the name of the TestPlan element to
refer the TestFragment.
"My" testers have renamed long time ago the TestPlan name but it did not impact
the tests until updating JMeter.
Now tests are failing and "my" testers must/will update all their scenarios and
it is not very comfortable accordingly to the amount of scenarios to update.

In the sametime, I've found that renaming the TestPlan name has still hazardous
propagation in particular in updating the related property of the
ModuleController about the TestPlan name reference.

>From the joined jmx file, here's a way to reproduce the issue.
The test has a TestFragment "TF-A" and a ModuleController "MC-A" that refers to
"TF-A" (see MC-FT-1.png).
Renaming TestPlan fomr "Test Plan" to "Test Plan 2", then saving and reopening
the test file do not take in account the renaming propagation that has to be
performed into the TestPlan reference inside the ModuleController to point to
the right TestFragment (see MC-FT-2.png).

But, if you rename the TestPlan name, then clicking on other TestTree elements,
the TestPlan reference in the ModuleController has been well updated (See
MC-FT-3.png).

Do you think it is possible to improve the renaming propagation to avoid such
reference issues?

thank you in advance for your support and maybe suggestions to help you in
fixing it.

-- 
You are receiving this mail because:
You are the assignee for the bug.
Mime
View raw message