Scanning a build
In order to collect coverage information SeaLights agents need to first scan the binary files for the build information: It can be the *.class, *.jar or even the *.war files.
Scanning a build in ANT using the Java Build scanner with the java task
Sample command
<target name="sealights_scan" depends="compile">
<java jar="${sealights.dir}/sl-build-scanner.jar" fork="true">
<arg value="-scan"/>
<arg value="-tokenfile"/>
<arg value="/path/to/sltoken.txt"/>
<arg value="-buildsessionidfile"/>
<arg value="buildSessionId.txt"/>
<arg value="-workspacepath"/>
<arg value="${build}"/>
<arg value="-r"/>
<arg value="-fi"/>
<arg value="*.class"/>
<arg value="-moduleName"/>
<arg value="${package}"/>
</java>
</target>
See 'Java Command Reference - Scanning a build' for full parameter details
Running tests using JUnit
In order to capture code coverage information from tests run with JUnit, you need to run it with our test listener as a Java agent:
- The listener needs to be passed using the jvmarg attribute -javaagent parameter together with its required parameters
Sample command
<junit fork="yes">
<jvmarg value="-javaagent:${sealights.dir}/sl-test-listener.jar"/>
<jvmarg value="-Dsl.tokenFile=/path/to/sltoken.txt"/>
<jvmarg value="-Dsl.buildSessionIdFile=buildSessionId.txt"/>
<jvmarg value='-Dsl.testStage="Unit Tests"'/>
</junit>
See 'Java Command Reference - Installing test listener as Java Agent' for full parameter details