Add screenshots as a first class part of the library

[craigfowler]

Screenshot support has been removed (because it was done manually). This should be added back in, with some options as to when to take them and where to store them.

Some options to consider:

• Take after a step failure
• Take after executing any 'Then' step

There also needs to be a mechanism for saving those screenshots somewhere.

[craigfowler]

It would be worth considering the screenshot advice on this page in order to simplify the API.

http://www.seleniumhq.org/docs/04_webdriver_advanced.jsp#taking-a-screenshot

So, perhaps two extension methods:

bool CanTakeScreenshot();

Screenshot TakeScreenshot();

This could then try the cast to ITakesScreenshot and gets out the native way if it's successful. If it's not then it tries using it as a remote Web Driver and getting it via the 'send remote command' mechanism instead.

---

An idea to decide when to take screenshots is to take them using a similar policy to Sauce Labs.

This would be to take a screenshot after performing any action which could change the state of the web page.

This could be detected with an attribute upon actions indicating that the change the state of the page. For example: [ChangesState].

Then, in the complete-performance event handler for an actor, we inspect the performable object instance. If it has that attribute then we take a screenshot.

---

I'd like to make this an action. The actor would do something like:

actor.Perform(TakeAScreenshot.Called("Some name"));

This would take a screenshot and save it with the given name. The actual filename would be prefixed by the test feature/scenario name and it would be saved at a configured path.

[craigfowler]

Migrated from csf-dev/CSF.Screenplay#43

[craigfowler]

What I'd like here is some kind of screenshot manager. That is - when any kind of screenshot is taken, it is automatically saved into an appropriate file location, with an appropriate filename.

Things I'd like to have when saving them:

• Base path for saved screenshots
• Feature identity (id and name)
• Scenario identity (id and name)
• Sequence of screenshots in scenario
• Screenshot name

Between these, I should be able to save the screenshot into a decent file path.

[craigfowler]

The way I'd like to do the above is to use a format string. The user should enter a formatted path string (using placeholders) to indicate where they'd like each screenshot saved. That path will be relative to the base path for screenshots.

The save mechanism will have a rule that it will recursively create any directories that are missing when saving those screenshots.

This is simple to understand and to administer.

[craigfowler]

Commit df1868c actually has nothing to do with this issue, it was a typo in the commit message.