[sanderjd]

Five minutes of tests really isn't such a big deal. Not long enough to bother re-architecting a bunch of stuff. But what frustrates me is that DHH seems to bullheadedly continue believing that problems they haven't had with Bootcamp simply aren't real problems. Bootcamp isn't all that big an app, so it isn't particularly surprising that the tests run that quickly. But once you get up into the high tens of minutes for unit tests, and the low hours for a full suite including end-to-end tests, it becomes really really annoying. Changing the architecture isn't going to help much or at all with those end-to-end tests, but it's easy to find yourself thinking "boy I wish we could at least get a bit of confidence in the correct functioning of our application in the face of this little change in less than half an hour - I wonder how we could accomplish that?". The three common answers once you find yourself wondering that are "let's parallelize our tests in the cloud!", "let's reduce external coupling in our tests!", and "let's make small services so any given change affects only a few tests!". All of those answers have fairly tough trade-offs.