Sublime

To the extent that we are able to embed testing practice inside development, we have created a process that is hyper-incremental where mistakes can be rolled back if any one increment turns out to be too buggy. We’ve not only prevented a lot of customer issues, we have greatly reduced the number of dedicated testers necessary to ensure the absence

find out if you’re really doing CI, ask your team the following questions: Are all the developers on the team checking into trunk (not just merging from trunk into their branches or working copies) at least once a day? In other words, are they doing trunk-based development and working in small batches? Does every change to trunk kick off a build pr

Test as you go, not at the end—a bug fixed now is cheaper than one that has had a chance to propagate through a system for months. Deliver product early and often, as only by demonstrating working software to your customer can you find out what they really want.