Home

This is currently a work in progress, but I’ll try to add information here to help people use the project.

Build Notes

In order to build toolkit, you must have at least ImageMagick executables identify and convert in your path.
You may also occasionally need to generate Certificates.

You will need to create a Firefox profile called “WebDriver”. Instructions for doing this can be found here. You should hit the running server and add a permanent exception for your self-signed certificate. This will allow the Selenium tests to run without error. (I realize there may be a bootstrapping problem here…I haven’t run into it myself, so I haven’t solved it either.) I also add the following key to the configuration, in order to keep Firefox from going into offline mode and failing my tests when I’m not connected to a network: network.manage-offline-status. If you set it to false, Firefox won’t put you in offline mode.

Running Tomcat In IntelliJ

Aside from the normal configuration steps, there are a few things you need to do in order to run Tomcat in IntelliJ.

1. Configure Tomcat for SSL
   Add the following to conf/server.xml with the keystoreFile modified for your environment.
   

   
         <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
                    maxThreads="150" scheme="https" secure="true" keystorePass="password"
                    keystoreFile="/Users/oliver/devel/toolkit/integration-test/src/main/resources/server.keystore"
                    clientAuth="false" sslProtocol="TLS" />
   

2. Add the AspectJ weaver to the VM arguments
   

   -javaagent:/Users/oliver/.m2/repository/org/aspectj/aspectjweaver/1.6.10/aspectjweaver-1.6.10.jar

3. Add the PATH for ImageMagick to your environment: if you’re running IntelliJ on a Mac and installed ImageMagick via ports, you probably won’t have the executables in the PATH that IntelliJ uses. See the following to add to your environment. I’ve found that adding a ~/.MacOSX/environment.plist like this:
   

   {
           PATH = "/opt/local/bin";
   }
   

   
   or adding an /etc/launchd.conf like this:
   

   setenv PATH /usr/bin:/bin:/usr/sbin:/sbin:/opt/local/bin:/opt/local/sbin

   
   both manage to effect the necessary path. The former is per-user, while the latter is system-wide.