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 …
I think you're imagining it in terms of existing tooling, though I'm expecting more would need to change. If you imagine the test gets checked when it's failing, and long before it's fixed, the workflow looks different.
-
-
So it's more like this situation: "We have a repo of tests for behavior X. Any code that implements behavior X should pass these tests."? Seems like a very open source, distributed workforce type of process that would work well on longer time frames between semi-coord. projects.
-
I haven't thought about it so concretely, but yes, definitely more along those lines.
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.