>You assume that you will write code and check in without testing. Code should pass all unit tests locally before check in. Some tools, like TFS, can be configured with a gated check in. If unit tests don't pass, check in is prohibited.

Perhaps I did assume that a bit. :)

My point was - the developer would check out the spark plug module and iterate through a set of different designs, with many failing the unit test(s). I'm using it to get a picture in mind. So the spark plug would be checked out the entire time? What if another developer discovered that platinum was a better core? That discovery made it through tests and into the main line. Would CI involve trickling that back to the spark plug module dev?

>
>>Craig. I often believe the software world can learn from other industries. So using an engine as a mainline branch. A developer wishes to refine the spark plug. That takes months of iterative testing and discarding unworkable designs. Why should any of these unworkable ones reach the mainline branch?