public sealed class CommandLogEverything a test has done, in order.
No guide page documents this yet — the page shows what the code says about itself.
Remarks
Cypress's best idea, and the one worth copying before any of the assertions: when a test fails, what you need is not the failing line but the twenty commands before it. A stack trace says which assertion threw; this says the interface had three buttons when the test expected one, that the click before it landed on the overlay, and that the assertion three steps back passed only after fifty-eight frames.
Kept unconditionally rather than behind a flag. A log switched on after a failure is a log for a failure that no longer reproduces, and the cost is a string per command in a test that is already building an element tree.
Fields and properties (1)
public IReadOnlyList<LoggedCommand> CommandsWhat has been done, in order.
Methods (1)
public override string ToString()The whole log, one command per line.
Used by (5)
- RetryTestsVixen.Ui.Testing.Tests
- ScreenshotTestsVixen.Ui.Testing.Tests
- UiSubjectVixen.Ui.Testing
- UiTestVixen.Ui.Testing
- UiTestExceptionVixen.Ui.Testing