You can still use the ModuleController, but only if you point it at elements under the TestPlan part of the test tree.
I don't think anyone is fixing it right now, but I could probably be talked into looking at it. -Mike On Wed, 2004-07-21 at 06:30, James Hughes wrote: > Hi. I have a very large test script and was hoping to use the Module > Controller to factor out the common parts of the script (and parameterise > for each time they are used). I will want to run this script from the > command line. > > The current documentation for Module Controller states that: > > "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." > > The documentation for Workbench says: > > "When you save your test plan, WorkBench items are not saved with it. Your > WorkBench can be saved independently, if you like (right-click on WorkBench > and choose Save)." > > Does this mean that the Module Controller is only of any use when using the > GUI? If so, are there any plans to tackle this to allow Module Controller > to be used when running from the command line? > > Thanks, > James. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Michael Stover <[EMAIL PROTECTED]> Apache Software Foundation --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
