|
|
Re: Suites for Suites
|
Posted: Apr 3, 2003 4:27 PM
|
|
> I'm attempting to extend SuiteRunner for my own purposes. > In doing so, I've refactored the Runner class and wanted > to make sure that in doing so I have not omitted/broken > any existing functionality. This leads me to my question. > I'm curious what your own purposes are. Any chance you could share with us what you're planning to do? We also have several enhancements in the works. I'm curious if there will be overlap.
Here are the main things we have planned in upcoming releases of SuiteRunner:
- ability to invoke and therefore test private and package access methods or public methods of innaccessible nested classes. - ability to specify user-defined properties in the recipe file (we're calling that Spice), and passing a Map of context name-value pairs in the Reporter. This is how we plan to enable users to pass context to tests. - making a few adjustments to facilitate testing distributed systems, including servlets, JSPs, EJBs, Jini systems, etc... Primarily, I'm considering changing the Thread in Report to a String threadName. This facilitates sending Reports between VMs without too much loss in the single-VM scenario. - fixing a few bugs - write more tests! We really need to have a test fest.
|
|