Imagine running tattoo on 50 elements, all of which pass on chrome, canary, firefox, and all of which fail on safari, because selenium is borked. We get a report 0/50 passed, and now have to manually dig through text logs to see why -- vs. -- seeing a summary of like
Can the tattoo summary output give some kind of summary/indication which browsers failed per element instead of just saying PASSED/FAILED/SKIPPED and the repo name?
This came from discussion on Slack today with @cdata and @notwaldorf (mentioning here in case they want to follow the issue or make suggestions)
wct has this nice summary it updates:
Imagine running tattoo on 50 elements, all of which pass on chrome, canary, firefox, and all of which fail on safari, because selenium is borked. We get a report 0/50 passed, and now have to manually dig through text logs to see why -- vs. -- seeing a summary of like
Can the tattoo summary output give some kind of summary/indication which browsers failed per element instead of just saying PASSED/FAILED/SKIPPED and the repo name?