JUnit Connection setup

2007-04-13 Thread Jürgen Weber
Hi, I want to run a JUnit-Test from Jmeter. During the test setup() should be called exactly once (to open a Corba connection), then the individual tests should be all run and then the connection be closed. The JUnit way to do this is use TestSetup

Re: JUnit Connection setup

2007-04-13 Thread Jürgen Weber
Yes, but [x] Do not call setUp and tearDown results in setUp() not being called at all, but I would like to have it called exactly once before the tests. Thanks, Juergen Alf Høgemark wrote: Hi I haven't tried your scenario myself, but I noticed that there is an option in the JUnit GUI Do

Re: SV: Error | Exception java.lang.OutofMemoryError

2007-04-03 Thread Jürgen Weber
I am trying to run a JacORB Corba client with jmeter. I am also constantly getting OutofMemoryError, even with 1 client and one thread. Without jmeter the client runs fine without memory options, so that would be the default of 128MB, I guess. -Oprindelig meddelelse- Fra: Aliasgar S

Re: CORBA sampler

2007-03-17 Thread Jürgen Weber
Shouldn't a Java or Junit sample not suffice to meter Corba clients? Do you want a sampler at the protocol level? This should be difficult, as the protocol contains no context information. IIOP data without the corresponding IDL is useless. Robert Spielmann wrote: Hi all, in accordance with

Re: CORBA sampler

2007-03-17 Thread Jürgen Weber
I wasn't clear, I meant of course load-testing the server, but this you can do by calling your Corba clients by a Java or Junit sampler. Some 64 jmeter Java sampler threads should indeed stress your server. Robert Spielmann wrote: Jürgen Weber schrieb: Shouldn't a Java or Junit sample

JUnit setUp() trap

2007-01-23 Thread Jürgen Weber
Hi, several JUnit tutorials (inclusive the sample at http://junit.sourceforge.net/javadoc/junit/framework/TestCase.html) show a protected void setUp() method. The JUnitSampler looks for the setUp() method using getMethod() but this finds only __public__ methods. So when you have a

Re: JUnit setUp() trap

2007-01-23 Thread Jürgen Weber
a bugzilla to enhance the user manual. sorry you had to waste time debugging your test. it's generally better to make the setup, teardown, onetimesetup and onetimeteardown public methods. peter On 1/23/07, Jürgen Weber [EMAIL PROTECTED] wrote: Hi, several JUnit tutorials (inclusive the sample