the reporting tool isn't done yet, but I have made some progress. You can see the latest screen capture here
http://woolfel.blogspot.com/2005/11/jmeter-progress.html I'm hoping over the holidays I can get the engine part done. progress has been slower than I would like, but I am making steady progress on it. peter On 12/2/05, Carsten Sensler <[EMAIL PROTECTED]> wrote: > > Dear Peter, > > can you explan how your reporting tool works? I'd like to use it, but i > doesn't know how it works and how i can use it für my specific JMeter > testscripts. > > Thank you. > > Best regards, > Carsten > > > -----Ursprüngliche Nachricht----- > > Von: Peter Lin [mailto:[EMAIL PROTECTED] > > Gesendet: Mittwoch, 2. November 2005 18:08 > > An: jmeter-user > > Betreff: [Summary of reporting tool approach] > > > > first off, thanks to everyone that responded. It really did help. Based > on > > the feedback, I'm thinking of going with the current approach for the > > reporting tool. > > > > Sample directory structure: > > > > - myDirectory > > - test plans (containing jmx files) > > - data (used in test plans) > > - logs ( containing jtl files) > > > > > > Going with the KISS approach, I'm considering the following approach. > > > > 1. the report plan provides a base directory for users to enter. for > > example, users would put "myDirectory/logs/" for the base directory > > 2. the reporting tool will load all the .jtl files in a given directory. > > It > > will not recursively scan sub directories and pick up the .jtl files in > > sub > > directories > > 3. the reporting tool will use the first timestamp in the .jtl file to > > determine the date the test was performed > > 4. the reporting tool will assume a single .jtl file contains the > results > > that should be considered 1 test run > > 5. the basic structure of the reporting tool is currently the following: > > > > report plan > > - report page > > - report table1 > > - chart1 > > - report table2 > > - chart2 > > - report page2 > > - report table3 > > - chart3 > > > > I'm still open to ideas, but hopefully this will generate some > discussion > > and feedback. > > > > peter lin > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
