Add code coverage support to Arcade SDK with VSTest integration #16206
Build #20251010.6 had test failures
Details
- Failed: 76 (0.42%)
- Passed: 17,188 (94.98%)
- Other: 833 (4.60%)
- Total: 18,097
Annotations
Check failure on line 32 in Build log
azure-pipelines / arcade-pr
Build log #L32
Artifact Logs_Test_Windows_NT_Release_Helix already exists for build 1170468.
Check failure on line 38 in Build log
azure-pipelines / arcade-pr
Build log #L38
Artifact Logs_Test_Linux_Debug_Helix already exists for build 1170468.
Check failure on line 1 in XunitReportingTests.ExerciseXunitCharacterFilteringFailurePath
azure-pipelines / arcade-pr
XunitReportingTests.ExerciseXunitCharacterFilteringFailurePath
Intentional Failure 🍕
Expected: True
Actual: False
Raw output
at XunitReportingTests.ExerciseXunitCharacterFilteringFailurePath() in Class1.cs:line 1
Check failure on line 1 in tests.UnitTest2.ExpectedFailureTheoryTest
azure-pipelines / arcade-pr
tests.UnitTest2.ExpectedFailureTheoryTest
Test failed
Check failure on line 1 in HelixReporter.TRXTests.HelixReporter.TRX.Fail2
azure-pipelines / arcade-pr
HelixReporter.TRXTests.HelixReporter.TRX.Fail2
This failure is expected and is not the reason why your PR failed. This test is always failing in order to test failure reporting infrastructure. If your PR is blocked there must be another test or build error that is blocking your PR.
Raw output
at tests.UnitTest1.TestMethod4() in UnitTest1.cs:line 26
Check failure on line 1 in HelixReporter.TRXTests.HelixReporter.TRXTests.Fail1
azure-pipelines / arcade-pr
HelixReporter.TRXTests.HelixReporter.TRXTests.Fail1
This failure is expected and is not the reason why your PR failed. This test is always failing in order to test failure reporting infrastructure. If your PR is blocked there must be another test or build error that is blocking your PR.
Raw output
at tests.UnitTest1.TestMethod1() in UnitTest1.cs:line 13