Running tests with MSTest or NUnit
When using MSTest or NUnit, the testStage argument can be added to the testListener command directly, and the test listener will monitor the tests. When test execution will be completed, test results will be uploaded automatically.
dotnet ./sl-dotnet-agent/SL.DotNet.dll testListener --buildSessionIdFile buildSessionId.txt --testStage "Functional Tests" --target c:\MyApplication\App.exe --workingDir c:\WorkingDir --targetArgs "-Flag1 true MyTest.dll"
POWERSHELL
Running tests manually using CLI
Starting a test stage
Before you start running your tests, you need to send the SeaLights server a start execution event with the test stages name
dotnet ./sl-dotnet-agent/SL.DotNet.dll startExecution --buildSessionIdFile buildSessionId.txt --testStage "Functional Tests"
POWERSHELL
Running your tests
Now you can run your tests while capturing coverage: https://sealights.atlassian.net/l/cp/w1EAHAFK
Uploading a report
Once the tests finish running you can upload one or more report files. Supported formats are MSTest (TRX files), xUnit.Net, and NUnit (XML files)
dotnet ./sl-dotnet-agent/SL.DotNet.dll uploadTestReport --buildSessionIdFile buildSessionId.txt --testStage "Functional Tests" --report myReport.trx
POWERSHELL
Ending the test stage
Once you are finished running your tests and uploading the results, you need to send the SeaLights server an end execution event with the test stages name
dotnet ./sl-dotnet-agent/SL.DotNet.dll endExecution --buildSessionIdFile buildSessionId.txt --testStage "Functional Tests"
POWERSHELL
