Using maven, include it as a dependency:

<repositories>    
    <repository>
        <id>jitpack.io</id>
        <url>https://jitpack.io</url>
    </repository>
</repositories>

<dependencies>
    <dependency>
        <groupId>com.github.willowtreeapps</groupId>
        <artifactId>conductor</artifactId>
        <version>3.0.0</version>
    </dependency>
</dependencies>

Create a Java Class, and extend it from io.ddavison.conductor.Locomotive

The latest drivers will be downloaded with the help of webdrivermanager and stored in the local maven repository.

Currently, six browsers are supported and they are Firefox, HTMLUnit, Chrome, Internet Explorer, Safari, and PhantomJS

The primary goals of this project are to...

• Take advantage of method chaining, to create a fluent interface.
• Abstract the programmer from bloated scripts resulting from using too many css selectors, and too much code.
• Provide a quick and easy framework in Selenium 2 using Java, to get started writing scripts.
• Provide a free to use framework for any starting enterprise, or individual programmer.
• Utilize the power of CSS!

Conductor can be configured using a yaml file. By default, Conductor looks for a config.yaml at the root of embedded resources.

The file has 3 sections: current configuration, defaults, and schemes.

The defaults section contains both Conductor defaults and a section to add custom desired capabilities to selenium. It looks like this:

defaults:
  browser: CHROME
  baseUrl: https://willowtreeapps.com
  timeout: 8
  retries: 10
  hub: http://hub.com/wd/lkajsd
  screenshotsOnFail: true
  customCapabilities:
    foo: bar
    fizz: buzz

Sometimes it is useful to specify properties under specific circumstances, and this is what "schemes" are for. Schemes override properties in the configuarion in the order they are specified in the currentSchemes section of the configuration file.

You might, for example, have a scheme for running on a specific device or specific remote testing tool. It's a pain to have to re-specify these so, Conductor makes this easy with schemes. Some example here we specify a scheme for shorter_timeouts:

currentSchemes:
 - shorter_timeouts
 
defaults:
  browser: CHROME
  baseUrl: https://willowtreeapps.com
  timeout: 8    # this will get overridden to 1
  retries: 10   # this will get overridden to 2
  hub: http://hub.com/wd/lkajsd
  screenshotsOnFail: true
  customCapabilities:
    foo: bar
    fizz: buzz

shorter_timeouts:
  timeout: 1
  retries: 2

You can see a variety of example configuration files in the unit tests for conductor here

Test classes can be annotated with @Config to add override the default browser or assign a path that will be appended to the default baseUrl.

@Config(
    path = "/ideas",
    browser = Browser.CHROME
)
public class IdeasTest extends BaseTest {
    
}

Conductor supports a couple of jvm env args that can be passed in to override some defaults:

• conductorCurrentSchemes to override the default currentSchemes
• conductorBaseUrl to override the default baseUrl (including ones specified on current schemes!)
  • This is specifically helpful when dealing with a dynamic url (e.g. Pull Request build with a unique build number).

mvn test -DconductorCurrentSchemes=shorter_timeouts,stage-dev

mvn test -DconductorBaseUrl=https://wta-stage-dev-pr-759.herokuapp.com

Supported methods can be separated by functionality into Actions, In-line validations, and helper methods for switching between windows and frames (listed below in more detail).

• For a full list of the supported APIs see the Conductor.java interface.

You can perform any action that you could possibly do, using the inline actions.

• click(By)
• setText(By, text)
• getText(By)
• hoverOver(By)
• check(By)
• uncheck(By)
• navigateTo(url)
• goBack()
• isPresent(By)
• getAttribute(By, attribute)
• etc.

This is one of the most important features that I want to accentuate.

• validateText
• validateTextNot
• validateChecked
• validateUnchecked
• validatePresent
• validateNotPresent
• validateTextPresent
• validateTextNotPresent

All of these methods are able to be called in-line, and fluently without ever having to break your tests.

Another nice feature that is offered, is the simplicity of window switching in Selenium.

• switchToWindow(regex)
• waitForWindow(regex)
• closeWindow(regex)

All of these functions take a regular expression argument, and match either the url or title of the window that you want to interact with.

• switchToFrame(idOrName)
• switchToDefaultContent()

In addition to the Selenium 2 implicit waiting, the AutomationTest class extends on this concept by implenting a sort of waitFor functionality which ensures that an object appears before interacting with it. This rids of most ElementNotFound exceptions that Selenium will cough up.

If you have an idea for the framework, fork it and submit a pull-request for the develop branch!

We follow GitFlow branch management reference graphic. The steps to make a new release are therefor:

1. Create a release branch from the develop branch named release/x.x.x
2. Create a new pull request from the release branch to the master branch
3. If approved merge release branch into master
4. Tag the merge (with release notes) in the master branch with x.x.x (this will make this version available in jitpack)
5. Create a new pull request from master to develop so all changes are back in develop
6. If approved merge master branch into develop