Selenium 2.0 builds with its own build technology that's good for Windows, Linux and Mac.
In the same directory as this file, do ...
The order of building modules is determined by the 'go' system itself. If you want to build an individual module (assuming all dependent modules have previously been build) try something like ...
As you see 'build targets' scroll past in the log, you may want to run them individually.
'Go' can run them individually, by target name as long as ":run" is appended (see above).
- Java 6 JDK
- "java" and "jar" on the PATH
Although the build system is based on rake it's strongly advised to rely on the version of JRuby in third_party/ that is invoked by "go". The only developer type who would want to deviate from this is the "build maintainer" who's experimenting with a JRuby upgrade.
- Python 2.6.x to 2.7 (without this, Python tests will be skipped)
Internet Explorer Driver
If you plan to compile the IE driver you also need:
- Visual Studio 2008
- 32 and 64 bit cross compilers
The build will work on any platform, but the tests for IE will be skipped silently, if you are not building on Windows.
For an express build of the binaries we release run the following from the directory containing the Rakefile:
./go clean release
All build output is placed under the "build" directory. The output can be found under "build/dist". If an error occurs while running this task complaining about a missing Albacore gem, the chances are you're using rvm. If this is the case, switch to the system ruby:
Of course, building the entire project can take too long. If you just want to build a single driver, then you can run one of these targets:
./go chrome ./go firefox ./go htmlunit ./go ie
As the build progresses, you'll see it report where the build outputs are being placed. Of course, just building isn't enough. We should really be able to run the tests too. Try:
./go test_chrome ./go test_firefox ./go test_htmlunit ./go test_ie
Note that the "test_chrome" target requires that you have the separate chromedriver binary available on your PATH.
If you are interested in a single language binding, try one of:
To run all the tests just run:
This will detect your OS and run all the tests that are known to be stable for every browser that's appropriate to use for all language bindings. This can take a healthy amount of time to run.
As a side note, none of the developers run tests using cygwin. It is very unlikely that the build will work as expected if you try and use cygwin.
Maven POM files
Ignore the Maven POM file present in the same directory. It is only used for releasing to jars to Maven Repository (public or local), and is not considered the main build mechanism.
"./go" only makes a top-level "build" directory. Outputs are placed under that relative to the target name. Which is probably best described with an example. For the target:
The output is found under:
If you watch the build, each step should print where its output is going. Java test outputs appear in one of two places: either under build/test_logs for junit or in build/build_log.xml for TestNG tests. If you'd like the build to be chattier, just append "log=true" to the build command line.
Help with 'Go'
More general, but basic, help for 'go' ...
Remember, "go" is just a wrapper around "rake", so you can use the standard rake commands such as "rake -T" to get more information about available targets.