A failing test suite tells you a number. The work is getting from that number to the line that br...A failing test suite tells you a number. The work is getting from that number to the line that br...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
A failing test suite tells you a number. The work is getting from that number to the line that broke.
The report is built as a narrowing path. Run history first, then a single run's summary with commit hash and environment so you know which build you're looking at. Then the test tree, carrying status inline so failures surface without expanding anything. Then assertion-level results for one case - each check with expected against actual, the raw validator output, and a diff that highlights only the values that changed.
Two decisions did most of the lifting. Status colour is load-bearing, not decorative: everything reads green, so red is the only thing your eye has to find. And when the expectation itself is stale (which is most failures on an actively changing API) Copy Actual to Expected resolves it in place, instead of sending you back to edit the test case.
Project: vRest NG.
Post image
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started