Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Gathering coverage and test information using the SeaLights Node.jsTest Listener is done in a few steps, we recommend to use the Lab ID for this. If your component does not yet support the Lab ID option, use the Build Session ID to connect between the test listener and the test runner:

Info

See 'Generating an Agent token' for instructions on how to generate a token prior to the commands

Starting the Test

...

Stage

First the SeaLights server needs to be notified that a test stage is starting.

Code Block
languagebash
Unix:
./node_modules/.bin/
npx slnodejs start --tokenfile /path/to/sltoken.txt --labid "<Lab ID>" --teststage "Unit Tests"

Windows:
call .\node_modules\.bin\npx slnodejs start --tokenfile \path\to\sltoken.txt --labid "<Lab ID>" --teststage "Unit Tests"

Expand
titleUsing Build Session ID
Code Block
languagebash
Unix:
./node_modules/.bin/
npx slnodejs start --tokenfile /path/to/sltoken.txt --buildsessionidfile buildSessionId --teststage "Unit Tests"

Windows:
call .\node_modules\.bin\ npx slnodejs start --tokenfile \path\to\sltoken.txt --buildsessionidfile buildSessionId --teststage "Unit Tests"
Info

See 'Node.js Command Reference - Starting a test stage' for full parameter details

Running your tests

...

Functional Tests

Before running your functional tests you need to set up the backend server to receive the test footprints. See 'Using Node.js Agents - Running backend server using SeaLights agent'

Once set up you now run your tests normally while generating one or more JUnit xml XML result files to be reported to the SeaLights server.

...

Unit Tests

As the unit tests Unit Tests are not run against a backend server, you need to run the actual tests using the Sealights Node.js Agent while generating one or more JUnit xml XML result files to be reported to the SeaLights server.

...

Code Block
languagebash
Unix:
./node_modules/.bin/npx slnodejs uploadReports --tokenfile /path/to/sltoken.txt --labid "<Lab ID>" --reportFile "/path/to/junit_report.xml"

Windows:
call .\node_modules\.bin\npx slnodejs uploadReports --tokenfile \path\to\sltoken.txt --labid "<Lab ID>" --reportFile "\path\to\junit_report.xml"

Expand
titleUsing Build Session ID
Code Block
languagebash
Unix:
./node_modules/.bin/npx slnodejs uploadReports --tokenfile /path/to/sltoken.txt --buildsessionidfile buildSessionId --reportFile "/path/to/junit_report.xml"

Windows:
call .\node_modules\.bin\npx slnodejs uploadReports --tokenfile \path\to\sltoken.txt --buildsessionidfile buildSessionId --reportFile "\path\to\junit_report.xml"

...

Code Block
languagebash
Unix:
./node_modules/.bin/npx slnodejs end --tokenfile /path/to/sltoken.txt --labid "<Lab ID>"

Windows:
call .\node_modules\.bin\npx slnodejs end --tokenfile \path\to\sltoken.txt --labid "<Lab ID>"

Expand
titleUsing Build Session ID
Code Block
languagebash
Unix:
./node_modules/.bin/
npx slnodejs end --tokenfile /path/to/sltoken.txt --buildsessionidfile buildSessionId

Windows:
call .\node_modules\.bin\npx slnodejs end --tokenfile \path\to\sltoken.txt --buildsessionidfile buildSessionId
Info

See 'Node.js Command Reference - Ending a test stage' for full parameter details

...