So writing a test would become (1) switch to a different repo, (2) branch, (3) write test, (4) push and make PR, (5) code review, (6) merge? That sounds awful.https://twitter.com/propensive/status/963086906954305536 …
For a start, you could lower the bar on code-reviewing tests because they hit touch deployable code, and don't even have to pass.
-
-
What's "hit touch deployable code"? And in your though experiment here, why would they not have to pass?
-
Sorry, s/hit/don't/. Swipo. The idea is that they wouldn't have to pass because all-tests-passing wouldn't be established as a precondition of any step in the workflow. Each code commit could potentially be tested against each test repo commit, and the changes tracked...
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.