Road Map
Current Road Map describes the features we would like to implement. We put together a good list that we (TW community) agreed should be our top priority.
Next Release
- Java & Ruby driver capability
- Concise, cut-down, binary downloads as well as complete source downloads
- Documentation for driver in addition to fitrunner
- Rename for driver and fitrunner (Latin influence).
TODO
- Drivers Dot-Net and Python (Ruby, Java in progress)
- Better Packaging (as per Hammant proposal)
- One download containing Java binaries and browserbot
- Another browserbot on its own (fitrunner mode)
- Another with source that can be rebuilt
- See the type of naming that Apache give src/bin downloads
- Better install instructions describing common architectures
- Make sure fitrunner/driven differences are well documented
- Complete Pet Soar Demo - Ryan ?
- Safari & Camino Support (Mac) - low pri.
- Launchers for Mac /Applications/Mozilla/mozilla-bin etc
- Windows launchers that use Runtime.exec() do not respond to process kill
- Continuous Integration
- Squid/Squirm/ebtables (refer that Freshmeat article).
- Ruby : Launch browsers as part of tests (and close them at end)
- Ruby: catch up with Java for getAllButtons() etc
- Both: rename getAllButtons() as per WATIR method names, if applicable
- Ant script : building of WAR file(s)
- Enhancement to Selenese - FQN of box driving tests should be forwarded to the browser (on launch) as a query string param, and back to the server in each response/request. Reason? A deployed 'bridge' servlet should be able to multiplex several testers.
- Investigate whether XUL, XAML have DOM models and could be scriptable via javascript - one day.
NOTE:
- Though we agreed not to put the funnel on the roadmap at this time, the need for it has been raised by many testing professionals. The Squid/Squirm avenue looks promising.
- We also agreed to maintain any other drivers that are submitted, such as the Squeek driver recently submitted. This has not been committed though.
