/show_bug.cgi?id=42139
Summary: Add more unit tests to
TestHTTPSamplersAgainstHttpMirrorServer
Product: JMeter
Version: 2.2
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P2
/show_bug.cgi?id=42139
--- Additional Comments From [EMAIL PROTECTED] 2007-04-17 01:54 ---
Created an attachment (id=19975)
-- (http://issues.apache.org/bugzilla/attachment.cgi?id=19975action=view)
Suggested patch
More unit tests, all should pass.
--
Configure bugmail: http
On 15/11/05, Peter Lin [EMAIL PROTECTED] wrote:
Hi sebb,
I was writing an unit test for the reporting and tried to run
TestSaveService, but I got some odd output in eclipse.
I used the JUnit tool in eclipse and tried to run the test. the output for
Setting JMeter home is bin\bin\
Can't
ahh ok. I'll give that a try
peter
On 11/15/05, sebb [EMAIL PROTECTED] wrote:
On 15/11/05, Peter Lin [EMAIL PROTECTED] wrote:
Hi sebb,
I was writing an unit test for the reporting and tried to run
TestSaveService, but I got some odd output in eclipse.
I used the JUnit tool in
Hi sebb,
I was writing an unit test for the reporting and tried to run
TestSaveService, but I got some odd output in eclipse.
I used the JUnit tool in eclipse and tried to run the test. the output for
Setting JMeter home is bin\bin\
Can't find jmetertest.properties - trying bin directory
My fault. I'm working on this. I would have sworn I ran the tests before
committing.
--
Salut,
Jordi.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-Original Message-
From: Jordi Salvat i Alabart [mailto:[EMAIL PROTECTED]
Sent: 03 December 2003 19:42
To: JMeter Developers List
Subject: Re: Unit tests totally broken
Well, none should ever fail (I mean when committing), so
reporting one
only just makes de clean-up process
ant test shows one failure more than it used to.
In addition, it now hangs.
:-(
We must all (including myself) learn to run the tests before checking.
--
Salut,
Jordi.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
.
Not sure about a hang, but it can be a bit slow.
S.
-Original Message-
From: Jordi Salvat i Alabart [mailto:[EMAIL PROTECTED]
Sent: 03 December 2003 11:27
To: JMeter Developers List
Subject: Unit tests totally broken
ant test shows one failure more than it used to.
In addition, it now hangs
a hang, but it can be a bit slow.
S.
-Original Message-
From: Jordi Salvat i Alabart [mailto:[EMAIL PROTECTED]
Sent: 03 December 2003 11:27
To: JMeter Developers List
Subject: Unit tests totally broken
ant test shows one failure more than it used to.
In addition, it now hangs.
:-(
We must all
Just to clarify and factor out possible platform differences: are you
seeing this unit test failure?
[java] 1)
testGUIComponents(org.apache.jmeter.junit.JMeterTest)junit.framework.ComparisonFailure: GUI-CLASS:
Failed on org.apache.jmeter.protocol.http.control.gui.AccessLogSamplerGui
Developers List
Subject: Re: Unit tests totally broken
Just to clarify and factor out possible platform differences: are you
seeing this unit test failure?
[java] 1)
testGUIComponents(org.apache.jmeter.junit.JMeterTest)junit.framework.Compari
sonFailure: GUI-CLASS: Failed
I've found the cause for this one: the failing test is checking that the
TestElements returned by two consecutive calls to
guiComponent.createTestElement() will be separate -- which is not true
for the AccessLogSamplerGui.
The only reason why it does not fail for the ProxyControlGUI (which
-Original Message-
From: Jordi Salvat i Alabart [mailto:[EMAIL PROTECTED]
Sent: 03 December 2003 12:50
To: JMeter Developers List
Subject: Re: Unit tests totally broken
Hmmm... it really looks like a hang. The test runs to completion (I see
the output FAILURES!!, and then:
[java
Salvat i Alabart [mailto:[EMAIL PROTECTED]
Sent: 03 December 2003 12:50
To: JMeter Developers List
Subject: Re: Unit tests totally broken
Hmmm... it really looks like a hang. The test runs to completion (I see
the output FAILURES!!, and then:
[java] FAILURES!!!
[java] Xlib: unexpected
The AccessLogSamplerGui holds a reference to an internal HTTPSampler,
and it stores values in it as well as in the individual GUI elements. Because
of the interaction of modifyTestElement, createTestElement, and
configure(TestElement), this double storing of values causes problems. The
I know it's not serious, but it doesn't help asking people to check for
clean unit tests before committing.
As a whole, I have a feeling that our TreeNode--TestElement--GUI
relationship (and the corresponding API semantics) is not as clean as it
should be. We'll need to work on that [again
fail; a single test can have
several failures.
S.
-Original Message-
From: Jordi Salvat i Alabart [mailto:[EMAIL PROTECTED]
Sent: 03 December 2003 13:30
To: JMeter Developers List
Subject: Re: Unit tests totally broken
[...] the test won't continue after that first failure.
Which is wrong
Mike is right. He and I had discussions about how to best handle validation at
runtime. I probably won't have time until next week to fix it, so feel free to clean
out AccessLogSampler.
the larger problem of how to handle runtime errors and pass the events back to the GUI
is a much larger
[mailto:[EMAIL PROTECTED]
Sent: 03 December 2003 13:30
To: JMeter Developers List
Subject: Re: Unit tests totally broken
[...] the test won't continue after that first failure.
Which is wrong: the test or the components
Drew,
My guess is that your enhancements to SizeAssertion introduced the test
failure below - can you please fix the problem or the test.
Thanks,
Scott
--
Scott Eade
Backstage Technologies Pty. Ltd.
http://www.backstagetech.com.au
.Mac Chat/AIM: seade at mac dot com
On 11/01/2003 1:10 AM,
Please remember to run ant test or ./build.sh test before committing
your changes.
[java] There was 1 failure:
[java] 1)
testGUIComponents(org.apache.jmeter.junit.JMeterTest)junit.framework.AssertionFailedError:
GUI-CLASS: Failed on org.apache.jmeter.assertions.gui.SizeAssertionGui
22 matches
Mail list logo
