This is a feature in development. more⇛

The main unit→ entry point can be specified on the command line. Alternately it may be specified as the item System.Main. This is useful in cases where all configuration data should come from a ptest→ file. more⇛

I had to download the latest selenium-rc to get testplan working with Firefox 3.6: more⇛

I had to add: more⇛

TestPlan 1.0 is considered a mature release. This generally means that any upgrades on this branch will be compatible with previous code. There are however some unclear bits still around, and in some cases logical defects which need to be addressed. more⇛

As a project grows you'll likely want to have proper functions defined for many of your test units. This simplifies the calling and results in a lot of code reduction. You can register one map of additional functions in the global properties. more⇛

ptest is the file format used to provide configuration data to TestPlan and your scripts. At first glance it will appear very much like a Java properties file. more⇛

If you intend on using Selenium on windows be aware that it doesn't work when instantiated from a network drive. This includes running it from a VirtualBox shared folder. more⇛

The StateLocale is a special construct which allows moving strings out of your test files into properties files. It provides a mechanism for language independence and easy lookup of keys based on the state. more⇛

TestPlan has many purposes and thus no one output, or logging mechanism, will be appropriate in all cases. The default output by TestPlan has been chosen to match some common use cases, though if it is not exactly what you want then you can use several options to control the output. more⇛