CI Dashboard with Quantum

When executing a Maven project, we can pass parameters to Maven. We know from CI Integration articles that Quantum expects the parameters reportium-job-name and reportium-job-number (see also CI Jenkins with Quantum). Therefore, when running the project as a Maven project, we can pass these parameters manually, for example by manually incrementing the build number by 1. For example, you can use the command line to run the following command:

mvn clean test -Dreportium-job-name=myJobName -Dreportium-job-number=42

Using Eclipse as IDE, we can do the same by creating a Run Configuration, where we can then simply pass different values per execution, as follows:

1. Click the pom.xml and select Run As > Run Configurations.

   

2. Create a new Maven build, setting the goals to include the params.
   

   

3. Apply the changes and run the build.

You can add an auto-incrementing build number that increases the build automatically every time the suite is triggered, for example by simply using the epoch time.

With Quantum, if we want to modify as little as possible (not creating new test listeners), we can use the pom.xml properties.

The following example by default sends the time stamp formatted a certain way as Job number (if no other parameter has been supplied executing the Maven project as in 1.)

We are using the maven build timestamp. In the first snippet, we set the way we want it formatted, as general properties right at the beginning of the pom.xml:

<properties>
    <maven.build.timestamp.format>yyMMddHHmm</maven.build.timestamp.format>
    ...
</properties>

Then we define the default system variables within the Surefire plugin paragraph:

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-surefire-plugin</artifactId>
    <version>2.19.1</version>
    <configuration>
        <argLine>-Dfile.encoding=${project.build.sourceEncoding}</argLine>
        <systemPropertyVariables>
            <reportium-job-name>phil_testCI</reportium-job-name>
            <reportium-job-number>${maven.build.timestamp}</reportium-job-number>
            <application.properties.file>resources/application.properties</application.properties.file>
        </systemPropertyVariables>
    ...
</plugin>

By setting the default values as in option 2, each test execution should be displayed under the default build name, with the current timestamp as the build number. If we now want to execute it as part of a different CI job name, we just need to set pass the -Dreportium-Job-Name parameter, and the build number will be supplied.