lundi 26 janvier 2015

Test driven development workflow for two programmers


We are currently starting with TDD and we want to work parallely in two programmers - one for writting test (Programmer A) and one for writting actual code (Programmer B). Problem is, how to synchronize our work.


Let's say A writes first test method, so B can start working on actual code. Our current workflow is that A will do commit/push, and B will pull his changes. In time it's bit annoying, because after every change in test (new test method/bug in current test method/some other update) requires commit/push/pull and it interupts both developers...


Is there some "best practices" for TDD? Some synchronization between their codes, mirroring, already existing tool etc? Thanks for any tip!





Aucun commentaire:

Enregistrer un commentaire