Executing tests on different environments

Executing tests on different environments

Each environment (e.g. develop, stable, staging) should be supported by separate instances.properties file. Environment selection should be handled on maven profile level

Bobcat configuration with Maven profiles

Project generated from archetype comes with one predefined profile:

<profiles>
    <profile>
        <id>integration</id>
        <properties>
            <configuration.paths>src/main/config/common;src/main/config/integration</configuration.paths>
        </properties>
    </profile>
</profiles>

To active profile in maven build add -Pintegration parameter.

mvn clean test -Pintegration

Overriding properties via command line -D option

You can also override properties by passing -D option to maven.

mvn clean test -Dconfiguration.paths=src/main/experimental-config -Dwebdriver.type=chrome

Each environment (e.g. develop, stable, staging) should be supported by separate maven profile.