Closed DrewML closed 9 years ago
A quick summary of each failure would be good - most of the time it's easy to see what went wrong. I also like the idea of a more advanced HTML output.
Found a solution where Protractor still displays the results in a friendly way, without needing a custom summary. Hooray for easy solutions.
This is in regards to #97.
I currently have a branch where we can run
ng-inspector
again n versions of Angular. The problem that I'm having is, I can't come up with an ideal way to visualize the test failures.Right now, by default, the Protractor runner will just pass the test results to stdout. The problem is, you'll have that output for each version of Angular, 1 by 1, and it's going to be a pain to scroll up and figure out which failures are from which version.
I currently have a setup in place that gives us the test results in the following format:
I've had different ideas of how to display these failures to a developer, but none of them seem ideal. The challenge is displaying all the useful data (version, suite name, spec name, stack trace), but grouped in such a way that it's not confusing.
My current idea: