Skip to content

Fix ConditionalAttribute tests to run without test case ordering

a4a9da9
Select commit
Loading
Failed to load commit list.
Merged

Update test deps to latest #16717

Fix ConditionalAttribute tests to run without test case ordering
a4a9da9
Select commit
Loading
Failed to load commit list.
Azure Pipelines / arcade-pr succeeded Apr 22, 2026 in 1h 9m 45s

Build #20260421.12 had test failures

Details

Tests

  • Failed: 48 (0.89%)
  • Passed: 4,924 (90.90%)
  • Other: 445 (8.21%)
  • Total: 5,417

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 XunitReportingTests.ExerciseXunitCharacterFilteringFailurePath

See this annotation in the file changed.

@azure-pipelines 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 HelixReporter.TRXTests.Fail1

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-pr

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