Page Comparison

When executing Tests via gradle you do not need Gradle against a build already reported to Sealights, you have to provide the buildSessionId generated in a previous step via an environment variable or a text file.

...

In order to use Sealights Gradle plugin, you’ll need to update your build.gradle file with relevant settings and enable its execution during the relevant Gradle projects.
For example, by adding the -Psealights property to your Gradle command.

Configuring Gradle plugin in build.gradle

In the repositories dependencies ‘repositories > dependencies’ section add:

1. classpath 'io.sealights.on-premise.agents.plugin:sealights-gradle-plugin:latest.release'

In the allprojects ‘allprojects’ section add the following:

1. apply plugin: 'io.sealights.on-premise.agents.plugin.sealights-gradle-plugin'

2. sealights section with the following parameters

   1. token or tokenFile - set with a token or a file containing the token obtained from the SeaLights dashboardSettings page

   2. buildSessionId or buildSessionIdFile - Set with a build session id or a file containing the build session id created externally via the config step, by the config step

   3. createBuildSessionId - Set to falsefilesStorage - location of temporary folder location to store cached agent files

   4. runTestOnly - Set to true if you want to only run tests without scanning builds

...

1. logEnabled - Set to true if you want a log to be created

2. logLevel - Set the log level to create. For example example WARN or INFO

3. logToFile - Set to true if you want the log to written to a file

4. logToConsole - Set to true if you want the log to written to the console

5. filesStorage - location of temporary folder location to store cached agent files

6. proxy - Provide the URL to the proxy to route the calls through if needed

7. testListenerJvmParams - Containing and array of all the parameters you want to pass to all the SeaLights test execution step, Note: the key and values must always be strings

8. testTasks - The list of tasks to integrate SeaLights into the jvmargs in. Default are test, unitPlatformTest & integrationTest

9. testStage - Provide the name of the test stage you want to report on in the SeaLights dashboard. Default stage name is 'Unit Tests'.

...

1. .

...

buildscript {
    repositories {
        mavenCentral()
        dependencies {
            if(project.hasProperty('sealights')){
	            classpath 'io.sealights.on-premise.agents.plugin:sealights-gradle-plugin:latest.release'
			}
		}
    }
}

allprojects { p ->
    if(project.hasProperty('sealights')){
        apply plugin: 'io.sealights.on-premise.agents.plugin.sealights-gradle-plugin'
        sealights {
            tokenFile = "./sltoken.txt" 
            createBuildSessionId = false
            buildSessionIdFile = "./buildSessionId.txt"
//          buildSessionId = System.getenv('SL_BUILD_SESSION_ID')

            testStage = "Functional Tests"
       	    filesStorage="/tmp"
            logEnabled = false
            logLevel = "WARN"
            logToFile = false
            logToConsole = true
            
            runTestOnly=true
            testTasks=["test"]
//          proxy = "http://localhost:8888"
//          testListenerJvmParams=["sl.param1":"true","sl.param2":"value"]
        }
    }
}

JUnit 5

When using JUnit 5 you need to notify the SeaLights agent that this is the case. You do so by passing sl.junitVersion=5 to the sealightsJvmParams

...