Cucumber JS framework

If your testing framework is Cucumber.js, the SeaLights agent integrates directly with it and reports the test results to the server directly.

See https://www.npmjs.com/package/sealights-cucumber-plugin for details.

Configuration

1

Installing Sealights plugin

npm install sealights-cucumber-plugin

2

Using the Sealights plugin with the Cucumber command

From the command line, add sealights parameters with --sl- prefix in addition to the --require argument specifying the Sealights plugin

node_modules/.bin/cucumber-js ./features --require sealights-cucumber-plugin --sl-tokenfile <path/to/token-file> --sl-buildsessionidfile <path/to/buildSessionId-file> --sl-testStage <test-stage-name>

Using the Sealights plugin with Protractor configuration

If you're running your Cucumber.JS tests with Protactor, in addition to the sealights-protractor-plugin, you need to specify in your protractor.conf.js file the required Sealights Cucumber plugin installed above.

cucumberOpts: {
    require: [
      './src/steps/*.steps.ts',
      require.resolve('sealights-cucumber-plugin')
    ]
  },

For more details about the sealights-protractor-plugin, please refer to the following page: https://www.npmjs.com/package/sealights-protractor-plugin

Parameters details

Parameter	Mandatory	Description
sl-token or sl-tokenFile	Yes	Access token generated from the SeaLights server provided directly or via the path to file containing it
sl-buildSessionId or sl-buildSessionIdFile	Yes	Session ID of configuration created passed explicitly (or using an environment variable or by providing the path to a file containing the Session ID.
sl-testStage	Yes	Name of the test stage
sl-labid	No	Unique ID for a set of test labs in case multiple labs are running simultaneously
sl-proxy	Optional	Address of proxy to run connection through

To enable logging, please refer to the slnodejs agent command reference documentation page: Logging