> Write the tests from outside in. With this, I mean you should write your tests from a realistic user perspective. To have the best quality assurance and refactor resistance, you would write e2e or integration tests.
Yah, yah. But good look trying to figure out what went wrong when only the failing test you have is an e2e or integration test.
My e2e tests automatically dump a multitude of debugging information and throw open a console from which I can quickly fire up code debuggers, logs, screenshots, network traces and browser traces in a few seconds.
Building test tooling is hard I'll grant you. It requires engineering chops and being up to date on the latest tooling. But not luck.
Yah, yah. But good look trying to figure out what went wrong when only the failing test you have is an e2e or integration test.