I'm stumped as to where the "Wrong test finished" message is coming
from.

Mike

On Apr 30, 2004, at 10:05 AM, ddchili wrote:

> Hi Mike, thanks for your response. I am using HttpUnit (1.5.4)
> TestCases where each have their own WebConversation object and I
> call the TestCases from a JUnit decorated suite by JUnitPerf in the
> following manner:
>
> int iterations = 1;
> Timer timer = new ConstantTimer(0);
>
> Test test = new TestMethodFactory
> (LoadNewUseCaseTestCase.class, "testLoadNewUseCase");
> LoadTest loadTest = new LoadTest(test, TestFrame.MAXUSERS,
> iterations, timer);
> Test cleanUpTestCase = new DeleteAllUseCasesTestCase
> ("testDeleteAllUseCases");
>
> TestSuite suite = new TestSuite();
>
> suite.addTest(loadTest);
> suite.addTest(cleanUpTestCase);
> return suite;
>
> The time to execute each test varies and the warning, "Wrong test
> finshed" message seems to happen when I have my tests run
> concurrently. If I set my ConstantTimer to allow for each test to
> complete before the next test thread starts, then I don't receive
> the warning. I named my threads a synchronized value and have
> determined that they all finish in order.
>
> Any ideas would be appreciated. Thanks again!
>
> David
>
> --- In junitperf@yahoogroups.com, Mike Clark <mike@c...> wrote:
>>
>> On Apr 20, 2004, at 10:34 AM, ddchili wrote:
>>
>>> Hi all,
>>>
>>> I'm running my httpunit test as a client and I'm using junitperf
> to
>>> do some basic load testing. I'm getting warnings stating the
> wrong
>>> test finished, but from what I can tell it's the first test
> started,
>>> and the first to stop. I added a synchronized static int to the
> test
>>> name to see test that the first test started was the first test
> to
>>> stop. I can get this problem if I run more than 1 LoadTest users
>>> (threads) and set my LoadTest timer (delay) to 0 milliseconds or
> a
>>> value under the time needed for the first test to complete.
> Here's
>>> the warning with running 5 users:
>>
>> The "Wrong test finished" warning isn't being issued by
> JUnitPerf.
>> Perhaps it's originating in HttpUnit.
>>
>> Can you share other details that might help diagnose the problem?
>>
>> Mike
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
Mike