While testing websites the response time of a page can be troublesome for the automated tests. Additionally JavaScript and/or page redirections can mean the page doesn't finish loading in the first request. more⇛

If you are sending emails as part of your web application is quite likely you will also send links as part of those emails. Links are usually used for confirmation, account information, or other purposes to direct a user to a specific part of a web application. more⇛

Clarification of how responses are handled within TestPlan with respect to protocols and rendering. Supports the Launchpad blueprint↗. more⇛

Just a kind of delayed note to say that I got the debug mode for HTMLUnit working. The retrieved files will now be stored in the Debug.Web file as with Selenium and HTTPUnit. more⇛

In order to test the reception of emails you will generally need to have an email address and POP server available. While you could get away with testing on a single address you'll discover quickly the limits that has. more⇛

TestPlan is an exceptional product for automating website activity. It has a lot of features and has been used with some very complex projects. As with all powerful products it can seem a bit daunting at first. This quick guide will help you take your first steps with TestPlan. more⇛

TestPlan contains a specialized testing language that we simply called "TPL". Files written in this language typically have the ".test" extension (which would explain why some docs may refer to the language as dottest still). more⇛

The current response, for the current stage, is accessible via the %Response% object. This will always be exposed in a XML-like structure suitable for Xpath navigation. See below for specific types. more⇛

Responses form the system are stored as the current response. All actions within .test which work with responses work on the most recent response. more⇛

As a quick example, the below uses the calculation function of Google to compute a simple arithmetic statement. more⇛