You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@jmeter.apache.org by pm...@apache.org on 2012/12/13 22:51:18 UTC

svn commit: r1421565 - /jmeter/trunk/xdocs/usermanual/component_reference.xml

Author: pmouawad
Date: Thu Dec 13 21:51:15 2012
New Revision: 1421565

URL: http://svn.apache.org/viewvc?rev=1421565&view=rev
Log:
Bug 54271 - Module Controller breaks if test plan is renamed
Bugzilla Id: 54271

Modified:
    jmeter/trunk/xdocs/usermanual/component_reference.xml

Modified: jmeter/trunk/xdocs/usermanual/component_reference.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/component_reference.xml?rev=1421565&r1=1421564&r2=1421565&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/component_reference.xml (original)
+++ jmeter/trunk/xdocs/usermanual/component_reference.xml Thu Dec 13 21:51:15 2012
@@ -2329,6 +2329,7 @@ For this reason it is best to ensure tha
 - as shown in the example above -
 otherwise a duplicate may be accidentally created when new elements are added to the test plan. 
 </p>
+<note>Renaming any element used in ModuleController implies updating Module to Run field</note>
 </description>
 <note>The Module Controller should not be used with remote testing or non-gui testing in conjunction with Workbench components since the Workbench test elements are not part of test plan .jmx files.  Any such test will fail.</note>
 <properties>