public sealed class UiTestOptionsWhat a test is allowed to do while it waits, and where its pictures live.
No guide page documents this yet — the page shows what the code says about itself.
Remarks
⚠ The retry budget is counted in frames, not in seconds, and that is the single most important decision in this assembly. Cypress waits on a wall clock because a browser it does not own is doing the work; here the test owns the loop, so "wait for the toast to appear" means "run frames until it appears" — which is deterministic, as fast as the machine can go, identical on a loaded CI runner and a quiet laptop, and replayable.
A wall-clock budget in the same place would have bought nothing and cost the property the repository's test conventions ask for by name: no Thread.Sleep, no ambient clock, no test that fails only when the machine is busy.
Fields and properties (8)
public int RetryFramesHow many frames a command may run before it gives up.
public TimeSpan FrameDeltaHow much the clock advances per frame.
public string? BaselineDirectoryWhere reference images are read from and written to.
public string? SourceBaselineDirectoryWhere an accepted baseline is written, when that is not where it is read from.
public string? ArtifactDirectoryWhere a failure writes what it saw.
public bool UpdateBaselinesWhether a screenshot rewrites its reference rather than checking it.
public ImageTolerance ToleranceHow far a screenshot may drift from its reference before it has changed.
public Color4 BackgroundWhat the interface is drawn on, where nothing else has been drawn.
Used by (9)
- RasterizerTestsVixen.Ui.Testing.Tests
- RetryTestsVixen.Ui.Testing.Tests
- ScreenshotTestsVixen.Ui.Testing.Tests
- UiSubjectVixen.Ui.Testing
- UiTestVixen.Ui.Testing
- VisibilityTestsVixen.Ui.Testing.Tests
- VisualBaselineVixen.Ui.Testing
- EditorSessionVixen.Editor.Testing
- EditorSessionOptionsVixen.Editor.Testing