You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 15, 2019. It is now read-only.
As a user debugging a major production issue module, caused by a module I have never worked on, one of the common questions is "what changed?" Therefore, I think there would be a lot of value in showing a 'last successful build' screenshot as well as the current 'after failure' screenshots (as well as html grabs). Maybe even a a markup diff feature at some point. All the above would be configurable in the event an operation's infrastructure cannot handle the extra file load. I am working on the Y! mod-dna project internally that would leverage the above, I'll showcase to you guys soon, which will take full advantage of these types of features as well.
Regards,
-A
The text was updated successfully, but these errors were encountered:
Also, can a screenshot be taken after each scenario, i.e. before browser window close, not just the last one? We have use case where we are running a chain of complex scenarios, but the screen shot will only come out for the last (failing) scenario.
andresn
changed the title
Configurable and enhanced screenshot functionality
Take screenshots after each failed scenario, not last one, and configurable and enhanced screenshot functionality
Apr 23, 2014
@andresn are you proposing it to be a cli/config option, so that user can choose if they want screenshot/html for every scenario step, or are you proposing this to be a default behavior for arrow ?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi Arrow Team,
As a user debugging a major production issue module, caused by a module I have never worked on, one of the common questions is "what changed?" Therefore, I think there would be a lot of value in showing a 'last successful build' screenshot as well as the current 'after failure' screenshots (as well as html grabs). Maybe even a a markup diff feature at some point. All the above would be configurable in the event an operation's infrastructure cannot handle the extra file load. I am working on the Y! mod-dna project internally that would leverage the above, I'll showcase to you guys soon, which will take full advantage of these types of features as well.
Regards,
-A
The text was updated successfully, but these errors were encountered: