Thanks! I've fixed the tests.
Just committed a fix for Bug 35370. Problem seemed to be that the Header class was using the test element name for the name of the header item, so I changed it to set a different property name. However, I've just realised that this invalidates all existing JMX files with Headers defined in them. So this needs to be replaced with a better fix that preserves existing test plans - or backed out. S. On 6/15/05, Michael Stover <[EMAIL PROTECTED]> wrote: > I'll take a look at the Runtime controller. The load tests probably > need to be remade in order to pass. > > -Mike > > On Wed, 2005-06-15 at 19:49 +0100, sebb wrote: > > Various JMS test elements have no documentation - Peter, are you doing > > all of these ? > > - Messaging Request > > - JNDI Default Configuration > > - LDAPArgument List > > > > I can create empty place-holders, but I don't know enough to be able > > to document them. > > > > There's a "new" bug in Runtime Controller - see > > http://issues.apache.org/bugzilla/show_bug.cgi?id=35059 > > > > I must have broken that when I fixed various other problems with the > > If, While and Once only controllers. Unfortunately I don't know how to > > fix it without breaking the others ... > > > > AFAIK, there's no test case for the RT C, which is presumably why the > > problem was not noticed earlier. I'm fairly sure that I can create a > > test-case, but fixing it is another matter. > > > > There are of course other bugs, but the RT used to work, so it would > > be good if it could be fixed. > > > > I still want to do some more fixes on HTTPsamplers and SampleResult > > etc, but they can wait. > > > > BTW, the test load and save tests are failing because various extra > > fields are being saved. > > > > S. > > On 6/15/05, Peter Lin <[EMAIL PROTECTED]> wrote: > > > I will finish writing the jms topic how-to and update the index number > > > this weekend. > > > > > > > > > peter > > > > > > > > > On 6/15/05, Michael Stover <[EMAIL PROTECTED]> wrote: > > > > What needs doing before we can release 2.1? As far as I'm concerned, > > > > we're ready for at least a release candidate. Sebb - any todos > > > > outstanding? > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
