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
