| Table of Contents |
|---|
Gathering coverage and test information using the SeaLights Python agent without a supported framework is done in a few steps:
| Info |
|---|
See 'Generating an agent Agent token' for instructions on how to generate a token |
Starting the test stage
First the SeaLights server needs to be notified that a test stage is starting.
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
sl-python start --teststage "Unit Tests" |
Running your
...
tests
Test Duration Requirements for Coverage Calculation
Please note that tests must run for a minimum of 1 second for SeaLights to calculate coverage. If your test duration is under 1s, adding a brief pause to your test will allow SeaLights to complete the coverage sampling process.
Functional Tests
Before running your functional tests you need to set up the backend server to receive the test footprints. See 'Using Python Agents - Running backend server using SeaLights agent'
Once set up you now run your tests normally while generating one or more JUnit xml result files to be reported to the SeaLights server.
...
Unit Tests
As the unit tests are not run against a backend server, you need to run the actual tests using the Sealights Node.js python Agent while generating one or more JUnit xml result files to be reported to the SeaLights server.
The command is the same as you would use on the backend server. See 'Using Python Agents - Running backend server using SeaLights agent'
Upload report files
Once done running the tests you upload the report files to the SeaLights server
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
sl-pthonpython uploadreports --reportfile "/path/to/junit_report.xml" |
Ending the Test Stage
Notify the SeaLights server that the test stage has ended.
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
sl-python end |