Skip to content

Provide an injection point for custom test reporting functionality #15775

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
RussKie wants to merge 1 commit into
base: main
Choose a base branch
from
+81 −0

Provide an injection point for custom test reporting functionality

e3c734c
Select commit
Loading
Failed to load commit list.
Open

Provide an injection point for custom test reporting functionality #15775

Provide an injection point for custom test reporting functionality
e3c734c
Select commit
Loading
Failed to load commit list.
Azure Pipelines / arcade-pr succeeded Apr 24, 2025 in 49m 14s

Build #20250423.12 had test failures

0 errors / 2 warnings

Details

Tests

  • Failed: 36 (0.41%)
  • Passed: 8,278 (94.69%)
  • Other: 428 (4.90%)
  • Total: 8,742

Annotations

Check failure on line 1 in HelixReporterTests.failure1

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-pr

HelixReporterTests.failure1 

Intentional Failure
Raw output 
            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.

Check failure on line 1 in HelixReporterTests.failure2

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-pr

HelixReporterTests.failure2 

Intentional Failure
Raw output 
            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.

Check failure on line 1 in HelixReporter.TRXTests.HelixReporter.TRX.Fail2

See this annotation in the file changed.

@azure-pipelines 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

See this annotation in the file changed.

@azure-pipelines 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
View more details on Azure Pipelines