THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Currently, Apache Avalon seems to be used for logging. Avalon seems to have stalled, should we move to log4j ?
- Would we gain functionality by moving to log4j ?
- Alternatively, move to Commons Logging (as used by HttpClient currently)
- Or perhaps SL4J - http://www.slf4j.org/
- What are the risks with continuing to use Avalon, if Avalon is not maintained anymore ?
Wiki Markup Remark: [HttpComponents] project is considering migrating [HttpClient] 4.0 branch off Commons Logging \[this was decided against: sebb\] to another logging framework as Commons Logging currently appears unmaintained \[not so: sebb\] and the prospects of its further development remain unclear. \[There has just been a new release: sebb\] It may be worthwhile to ensure both projects use the same logging framework / compatible logging frameworks. \[Agreed: sebb\]
- Reorganise documentation
- component_reference is getting much too big. This will require changes to the help system.
- sort functions and component ref into more logical order (currently chronological)
- perhaps use separate XML files for each item, included by main pages ?
- Could we then add a "Help" button to each GUI element, which would bring up the correct help in the browser ?
- or extend the existing help menu to load just the individual page.
- If there are combined and individual help pages, there would probably need to be two copies. Maybe simplest just to split component reference by element type; keep current page as an index into the subsections
- Help could perhaps be extended to allow loading of linked pages (but one would probably not want to allow external links to be loaded). There is some code in View Tree that might help here.
- Re-write ClassFinder:
- needs general tidyup / javadoc
- cache results - same classes may be requested multiple times
- TestBean:
- prepare is probably called too often; can it be done once per test?
- need some more GUI types - eg. table
- would be nice to be able to enable/disable fields depending on what else is selected - e.g. JDBC parameters only needed for prepared statements
- ensure drop-down list size big enough for all entries (within limits!)
- move from Bugzilla to JIRA? More flexible, (but attachments a bit more awkward at present?)
- JMS GUIs should be loadable without needing JMS jars (needs an extra level of indirection, as is done by JMS Publisher) or as below.
- How to handle Gui elements that depend on optional jars:
- should these be displayable, even though the jars are missing? Convenient for creating and viewing test pans, but not so useful at run-time - should the test plan be allowed to run?
- or should they be omitted as at present? - this is confusing at build time.
- or perhaps generate a dummy entry in the list, with a message to say the jar is missing? his would be tricky, as the class is needed to retrieve the name and the menu category. Perhaps the way to do it is to handle it in the GUI by catching the errors, and changing the name or screen comment? May be tedious to do.
- Sort test tree according to JMeter processing order? This should probably be a separate action, as it would be confusing for the tree to change as it was editted! (the menu drop-downs are now in the correct order)
- GUI code refactor
- there are various table implementations, could they be combined?
- perhaps the table models could also be combined?
- Add SVN revision number to version? (already added to Manifests)
- Consider migration to Maven2 as a build tool for JMeter. This should help simply dependency management and facilitate the use of JMeter for automatic load testing / integration into tools like Continuum
- Maven 1 was tried a couple of years ago, and seemed incompatible with the JMeter directory layout and multiple jars; hopefully Maven 2 is more flexible.
- Consider renaming ThreadGroup as JMeterThreadGroup - or UserGroup ? - to avoid confusion with java.lang.ThreadGroup
- Documentation refers to threads and/or users in different places; replace by users - or users(threads) - everywhere?
- Test elements need access to ThreadGroup and TestPlan for co-ordinating counts etc per-group and per-plan. Not much distinction is currently made between per-group and per-plan.