No, you're not doing anything wrong. A testplan file doesn't specify a workbench file. It should, we all agree.
To get around this, you'll have to find room in your test plan for these alternate modules. I'd recommend a ThreadGroup scheduled to run....never. I've never tried that, though, so I'm just throwing that out there. Others might have better suggestions. This also goes along with my desire to define test execution packages for JMeter, which would include everything needed to execute a test plan to allow a user to create the package, put it on an entirely different machine, and run it without any fudging necessary. -Mike On 18 Sep 2003 at 15:03, Pete Luellen wrote: > I'm new to JMeter (great tool) and am having a little trouble executing a test plan > containing ModuleControllers via command line. Here are the steps I go through: > > 1. I created and saved several modules, then reopened them into the workbench so that they would be available to ModuleControllers. > > 2. In a new test plan I added several ModuleControllers each referencing a different module created in step 1. > > 3. I executed the test plan successfully via GUI - it produced sample results. > > 4. When I executed the test plan via command line, I get no results (literally, "<testResults>") in my output file. > > I am able to run other test plans (that do not contain module controllers) with results via command line. > > I think this may have something to do with there being no capability of setting a workbench when executing from the command line (since the ModuleController relies on the workbench to reference an existing module). > > Am I doing something wrong? Has anyone else experienced this problem? > > Thanks in advance for the help. > > Pete > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jmeter-user- [EMAIL PROTECTED] > For additional commands, e-mail: jmeter-user- [EMAIL PROTECTED] > -- Michael Stover [EMAIL PROTECTED] Yahoo IM: mstover_ya ICQ: 152975688 AIM: mstover777 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
