By default TestPlan will use an internal browser, such as HTMLUnit. To test in an actual browser you can however use Selenium. more⇛

When an error occurs during a test it is often helpful to determine where in your program you were, or more particularly the content of the HTML page. more⇛

If the basic execution as described in Getting Started→ does not meet your needs you may need to invoke some of the additional command-line options. more⇛

A file, or script, can be referenced TestPlan in the scripting language, on the command line, or via Java module. These files are all resolved via a common resolution pattern. more⇛

This document explains how to setup an FTP server for testing. This doubles as the required setup to build the TestPlan release. more⇛

If you wish to have an FTP server for testing, or for running the TestPlan tests these simple instructions will help you. more⇛

XML allows creation of documents spanning several namespaces. These namespaces must be available to the XPath query system otherwise you will be unable to locate the elements. 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⇛

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⇛

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⇛