On 8/3/05, sebb <[EMAIL PROTECTED]> wrote:
> On 03/08/05, Henri Yandell <[EMAIL PROTECTED]> wrote:
> >
> > 2 aren't a problem, two do seem to be a problem. Looking at the files
> > involved in the missing tags, I suspect it's not a huge problem, but
> > it's disquieting to have failings. I'll join
woolfel 2005/08/04 21:13:33
Modified:src/protocol/http/org/apache/jmeter/protocol/http/control/gui
WebServiceSamplerGui.java
Log:
fixes the bug I accidentally introduced. already fixed in 2.1 branch. now
making the
change in HEAD
peter
Revision Chan
woolfel 2005/08/04 21:04:12
Modified:src/junit/org/apache/jmeter/protocol/java/control/gui
JUnitTestSamplerGui.java
Log:
added suite() method in the method filter. thanks to sebb for suggesting it.
peter
Revision ChangesPath
1.11 +4 -2
In due course, yes, I believe so.
Just thought I'd experiment with those two, as they did not need any
special access to private fields etc, and I was anyway changing one of
them.
S.
On 05/08/05, Peter Lin <[EMAIL PROTECTED]> wrote:
> I forget, are we planning on moving all JUnit tests out to the
I forget, are we planning on moving all JUnit tests out to the test directory?
peter
On 4 Aug 2005 21:27:51 -, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> sebb2005/08/04 14:27:51
>
> Modified:src/protocol/http/org/apache/jmeter/protocol/http/sampler
>
sebb2005/08/04 16:48:08
Modified:src/protocol/tcp/org/apache/jmeter/protocol/tcp/sampler
TCPSampler.java
Log:
Close socket if an error is encountered
Revision ChangesPath
1.14 +15 -11
jakarta-jmeter/src/protocol/tcp/org/apache/jmeter/p
sebb2005/08/04 16:30:47
Modified:src/protocol/tcp/org/apache/jmeter/protocol/tcp/sampler
TCPSampler.java
Log:
Use ThreadListener rather than TestListener to close socket at end
Revision ChangesPath
1.13 +20 -75
jakarta-jmeter/src/proto
The only pain I ever had building the client from source was
remembering to make sure SSL was installed before-hand.
Building the server was a different story, I found it very painful.
I'll try to find the configuration line I was using to build from
source. It was pretty simple.
Hen
On 8/3/05,
sebb2005/08/04 14:27:51
Modified:src/protocol/http/org/apache/jmeter/protocol/http/sampler
HTTPSampler.java
Added: test/src/org/apache/jmeter/protocol/http/sampler
HTTPSamplerTest.java
Log:
Move test code to test tree
R
sebb2005/08/04 14:17:07
Modified:src/protocol/http/org/apache/jmeter/protocol/http/sampler
HTTPSampler2.java
Added: test/src/org/apache/jmeter/protocol/http/sampler
HTTPSampler2Test.java
Log:
Change to use new ThreadListener
sebb2005/08/04 14:16:58
jakarta-jmeter/test/src/org/apache/jmeter/protocol/http/sampler - New
directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
sebb2005/08/04 14:16:58
jakarta-jmeter/test/src/org/apache/jmeter/protocol/http - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
sebb2005/08/04 14:16:58
jakarta-jmeter/test/src/org/apache/jmeter/protocol - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
sebb2005/08/04 14:15:48
Modified:src/protocol/jms/org/apache/jmeter/protocol/jms/sampler
JMSSampler.java
Log:
Change to use new ThreadListener interface
Revision ChangesPath
1.10 +4 -5
jakarta-jmeter/src/protocol/jms/org/apache/jmete
sebb2005/08/04 14:15:21
Modified:src/core/org/apache/jmeter/testelement
AbstractTestElement.java TestElement.java
src/core/org/apache/jmeter/threads JMeterThread.java
Added: src/core/org/apache/jmeter/testelement ThreadListener.java
Lo
sebb2005/08/04 14:10:54
Modified:.build.xml
Log:
Minor tweak
Revision ChangesPath
1.208 +4 -4 jakarta-jmeter/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-jmeter/bui
I was think to write/configure the report settings.
peter
On 8/4/05, Michael Stover <[EMAIL PROTECTED]> wrote:
> I'm not sure what the point of the gui is. Although it's nice to show a
> report gui, there are other tools for that. I'm thinking these report
> generators are essentially creatin
I'm not sure what the point of the gui is. Although it's nice to show a
report gui, there are other tools for that. I'm thinking these report
generators are essentially creating output for
excel/staroffice/jasperreports/image viewers/etc - not for JMeter. A
gui in JMeter could assist to control
On 04/08/05, Michael Stover <[EMAIL PROTECTED]> wrote:
> Yay Apache and licensing issues...
>
> It sounds to me like a reporting framework should not be linked to
> JMeter's gui in any way - it serves no purpose. What is needed is an
> extendable framework for writing reporting components that ta
This would make more sense. As long as each component basically took a
.jtl file and either wrote the report to disk or [if possible] display
the report in a gui. That way each component could generate the report
using the best strategy for that type of report. Maybe xslt for html
reports, JRXm
JCharts uses apache style license, so we can use that for the charts
and graphs. in terms of reports, it might be nice to have a separate
reporting GUI. Though I was thinking of taking the easy way out and
have it be a normal jmeter plugin that loads in the same gui
peter
On 8/4/05, Michael Stov
Yay Apache and licensing issues...
It sounds to me like a reporting framework should not be linked to
JMeter's gui in any way - it serves no purpose. What is needed is an
extendable framework for writing reporting components that take a .jtl
file and convert it to whatever report a user wants. R
the idea of using jasper reports sounds nice, but not sure about
license issues, since jasperReports uses LGPL license.
peter
On 8/4/05, Joseph Fifield <[EMAIL PROTECTED]> wrote:
> This is basically what I did with xslt to generate the html reports when
> I did the ant task. What about doing som
This is basically what I did with xslt to generate the html reports when
I did the ant task. What about doing something similar to generate
reports in other formats? This should be relatively straightforward for
something like JasperReports as the report files are just xml anyway.
Joe
Peter L
yeah, I was thinking the same thing. this way, in an automation
process, it might run several test plans and save the JTL files to a
specific directory.
after the tests are done running, jmeter could be called to process
the JTL files and output the reports.
peter
On 8/4/05, sebb <[EMAIL PROTEC
It would be useful if the Reporters could read existing test logs in
non-GUI mode too - assuming of course that the relevant raw data has
been logged.
S.
On 04/08/05, Peter Lin <[EMAIL PROTECTED]> wrote:
> you're right, there probably needs to be a GUI component for creating
> the report settings.
you're right, there probably needs to be a GUI component for creating
the report settings. the primary difference between the simple data
writer and report components is the reports would be for statistics.
for example, say an user has an overnight automation process that hits
a website. if the us
There surely still needs to be a GUI to configure the Reporter?
There is already a Listener that creates output to disk only - Simple
Data Writer.
Would it not be simpler to extend the existing structure with new or
amended Listeners that write to disk rather than the screen?
Not that I mind the
Peter,
I'd be interested in helping on this. My main interest would be extending the
abstract class to dump out to a reporting framework, like JasperReports.
--Tom
On Thursday, August 04, 2005, at 10:27AM, Peter Lin <[EMAIL PROTECTED]> wrote:
>Hey sebb,
>
>mike and I were just chatting abo
Hey sebb,
mike and I were just chatting about some enhancements to JMeter. I was
thinking, it might be nice to be able to run jmeter in console mode
and have it dump out graphs or statistics. My thought was to do the
following.
1. create a new type of component called Report
2. there would be an
BTW, just noticed that the JUnit Sampler only checks for methods
called "test..." - should it not also allow for the suite() method?
Might also want to consider whether the junit classpath property
should allow both directory names and individual jar files.
E.g. split the string using the JVM cla
On 04/08/05, Steven Murphy <[EMAIL PROTECTED]> wrote:
> Sorry I should have mentioned that I am launching JMeter inside NetBeans, I
> thought that because of this I didn't need to put the class files into a jar
> file until I wanted to run it outside of the IDE. Is this wrong? Should I
> include
The issue is that there's a difference between the JMeter classpath and
the search path that JMeter will search for classes that extend JMeter
core classes. Searching the entire classpath could take a long time -
JMeter is already a slow enough starter.
I can't speak to the netbeans setup, as I'm
that's a much better and more flexible way of handling it than my
simple first attempt.
I'll make that change tonight, and add the property to
jmeter.properties. by the way, thanks for all of your suggestions.
the sampler now provides default values.
peter
On 8/4/05, sebb <[EMAIL PROTECTED]>
The latest version of JMeter generates an error message in the console
window unless the lib/junit directory exists. Presumably this is
intended for holding jars containing JUnit tests?
Seems unnecessary to have to create an empty junit directory even if
one is not using the JUnit sampler.
Would
woolfel 2005/08/04 06:53:10
Modified:src/core/org/apache/jmeter DynamicClassLoader.java
Log:
really stupid and silly mistake on my part. this.addURL does a great
job of causing stack overflow. it should be super.addURL. thanks to
sebb for pointing out my brain dead mistake.
pet
Sorry I should have mentioned that I am launching JMeter inside NetBeans, I
thought that because of this I didn't need to put the class files into a jar
file until I wanted to run it outside of the IDE. Is this wrong? Should I
include these 2 classes in the ApacheJMeter_components.jar file?
Where have you put your jar that contains the new classes? If you put
it in /lib, it will be in JMeter's classpath, but not in the path it
searches for new components. If int /lib/ext, then it should be found.
-Mike
On Thu, 2005-08-04 at 14:00 +0100, Steven Murphy wrote:
> I would need to exten
I would need to extend the AbstractControllerGui right?
I think the problem might be that my classes are not being executed when
JMeter is loaded.
As I'm not all that familiar with java I have copied the ModuleController
and ModuleControllerGUI classes, to use as a templates. I have changed
This should happen automatically if the GUI element extends the
correct base class.
S.
On 04/08/05, Steven Murphy <[EMAIL PROTECTED]> wrote:
> I'm sure this is very simple to do, but I'm having trouble finding how to
> add a new option to the Logic Controllers menu.
>
> I've had a search though t
I'm sure this is very simple to do, but I'm having trouble finding how to
add a new option to the Logic Controllers menu.
I've had a search though the MenuFactory and JMeterMenuBar classes but I
can't find where the indvidual menu items are beong added.
Could someone point me in the right dir
41 matches
Mail list logo