UX (console slow to load) & $ saving - make tests the default tab on finished builds

[nealeu]

When opening a failed build, e.g. from a Slack notification, I want to get to the "tests" tab to see the test failure summary but have to wait while several meg of console is loaded.

The user experience here could be improved and would hopefully also result in some cost savings for Shippable.

Would you consider improving this please.

Solutions could be:

• Automatically show the tests tab the default if there are test failures
• Provide an option to make tests tab the default on a completed build. I say that this should be optional because some users will only look at build failures in the console for their build tools.
• Alternatively defer loading the console if the size is large, and allow click to load.

I think making the tests tab show by default when there are test failures is probably the best UX, as it keeps the default behaviour for people who don't use that feature, but saves on time and bandwidth for those of us that do.

Keep up the great work. I really appreciate Shippable.

[nealeu]

This one has been around a while, and I don't think it's that difficult to implement.

Having hit this again from a low bandwidth connection, I'm thinking that this should not just be "on failure" but on any completed build or "if there are any test results".