It should be OK to change the package names in this code to those of webdriver.

Absolutely. In fact, if the project chooses to use the provided code, they are of
course free to decide how they want to incorporate it with Webdriver. E.g. let it be
a standalone module, or include it in one of the existing modules.

The package name is a slip-up on our behalf, and should indeed be changed to a more
appropriate name.

Yes. Absolutely. Likely has to be Java for is-it-on-the-machine-ness. Also should include
'remove -htmlSuite from the server' as this would be replacement tech.

The way of running the Selenium HTML scripts, ie. interpreting them instead of compiling
them into Java, has some major advantages:

1. Allows for easy incorportion with your Continuous Integration process:
a. A tester (usually a non-techi) records a test case/suite through the Selenium IDE
and
saves it in Selenium HTML.
b. These Selenium HTML scripts are checked in into a version control system (eg. Subversion).
c. A programmer builds a Java program that loads and runs each script as a JUnit test.
(This could be a program a little more sofisticated than GoogleTest.java example above,
for it wil load and run all scripts present in a certain directory. Allowing for testers
to add scripts without need to modify the Java program.)

2. In case a new Selenium API is released you will not have te export all scripts again
to Java files. Simply replacing the interpreter is all that is needed. You won't have
to export the scripts at all, nor adding the exported Java file to your version control
system to incorporate them into your Continuous Intergration build process.

3. Similar interpreters could be created for other languages such as Ruby, Python,
C#, etc. This way Selenium HTML could become a standard test DSL (Domain Specific Language).

This is the Holy Grail of web testing! Looks like somebody else is on the case http://code.google.com/p/mvnsese/

Writing a runner for selenese is out of scope for the project. That said, one of the
project's GSoC students has been working on the problem this summer. It takes
- selenese -> remote webdriver
- setup/teardown (in xunit style)
- data driving

The code is at https://github.com/Toseter/SeleniumRunner

Documentation, etc. coming in the next week or so.

(there is also http://www.selunit.org/ and a number of other ones).

For those of you still looking for this, the following project works very nicely and
is actively maintained: https://github.com/vmi/selenese-runner-java