public sealed class UiTestExceptionA command that could not be satisfied within its budget.
No guide page documents this yet — the page shows what the code says about itself.
Remarks
Its own type rather than an assertion-library failure, because this assembly must not choose one. A project asserting with Shouldly, xunit's Assert or nothing at all gets the same exception, and a test runner shows the message either way.
⚠ The message carries the command log and the tree, not just the claim that failed. "Expected 1 element matching '.toast', found 0" is a true statement that tells nobody anything: the question is always whether the selector is wrong, the element never appeared, or something earlier in the test did not do what it looked like it did. So the log answers the third, the tree answers the first, and the count answers the second.
Methods (3)
public UiTestException(string message)Creates a failure.
public UiTestException(string message, Exception inner)Creates a failure with an inner cause.
public UiTestException()Creates a failure with no message. Present because the analyser asks for it.
Used by (9)
- InteractionTestsVixen.Ui.Testing.Tests
- OverlayInteractionTestsVixen.Ui.Controls.Tests
- QueryTestsVixen.Ui.Testing.Tests
- RetryTestsVixen.Ui.Testing.Tests
- ScreenshotTestsVixen.Ui.Testing.Tests
- SelectorQueryVixen.Ui.Testing
- UiSubjectVixen.Ui.Testing
- VisibilityTestsVixen.Ui.Testing.Tests
- VisualBaselineVixen.Ui.Testing