If your testing framework is Cucumber.js, the SeaLights agent integrates directly with it and reports the test results to the server directly.
...
| Code Block |
|---|
npm install sealights-cucumber-plugin |
Using the Sealights plugin
...
with Cucumber command
From the command line add sealights parameters with --sl- prefix in addition to the --require argument to specifying the cucumber commandSealights plugin
| Code Block | ||
|---|---|---|
| ||
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
In addition to the sealights-protractor-plugin, you need to specify in your protractor.conf.js file the required Sealights Cucumber
...
From the command line add sealights parameters with --sl- prefix
| Code Block | ||
|---|---|---|
| ||
TBD |
...
plugin installed above.
For more details about the sealights-protractor-plugin, please refer to the following page:
| Code Block |
|---|
cucumberOpts: {
require: [
'./src/steps/*.steps.ts',
require.resolve('sealights-cucumber-plugin')
]
}, |
Parameters details
Parameter | Mandatory | Description | ||
|---|---|---|---|---|
| Yes | Access token generated from the SeaLights server |
| Path provided directly or via the path to file containing access token generated from the SeaLights serverit |
| Yes | Session ID of configuration created |
| Path to passed explicitly (or using an environment variable or by providing the path to a file containing the Session ID of configuration created. |
| Yes | Name of the test stage | ||
| No | Unique ID for a set of test labs in case multiple labs are running simultaneously | ||
| Optional | Address of proxy to run connection through |
| Info |
|---|
To enable logging, please refer to the slnodejs agent command reference documentation page: SeaLights Node.js agent - Command Reference | Logging |