Do not try to use ./.jenkins_test/ since the actual location is unpredictable (varies acc. to CWD of Maven JVM).
Show test output on console when running single test suites or cases, just not when running the whole project.
Allowing some important environment variables to be defined via Maven property.
Thus you can add to your ~/.m2/settings.xml something like:
        <profile>
            <id>acceptance-test</id>
            <properties>
                <BROWSER>chrome</BROWSER>
                <JENKINS_WAR>/tmp/jenkins-1.554.1.war</JENKINS_WAR>
            </properties>
        </profile>
and then just:
$ mvn -Pacceptance-test test
Doc improvement
Refactoring out the interaction with outgoing email service.
typo
Moving selenium specific logic into a sub-package
Revisiting the way we handle "Element is not clickable at point (506, 967). Other element would receive the click" problem.

Jesse reminded me that Oliver did a more "proper" hack in the capybara layer back in the old selenium-tests project, so I've resurrected the code.