Automatic screenshots.

[charleslbryant]

Screen shots are helpful in proving the results of a test run or helping to research a test failure.

We could have a feature that automatically triggers a screen shot on test failure or exception.

We may even be able to add an attribute or method that would trigger a screen shot on a test step. When the runner finds the attribute on a step method, after the step runs take a screen shot.

Also, we could have a feature where every step is captured, test recording. We could configure for every test in a suite or feature.

For example we could change TestPipe Browser API to expose functionality similar to WebDriver C# EventFiringWebDriver. Then TestPipe can catch events to trigger screen shots.

[charleslbryant]

In addition to the EvenFiringWebDriver, which may cause some issues, we could expose this functionality in TestPipe.Assertions (screen shot on specific asserts and assert method overloads), in the wait functions (e.g. trigger on timeout exceptions), and maybe in the runner (e.g. Tarsvin, screen shot on exception).