swsnu / wecfall2014

0 stars 0 forks source link

testing and source control #20

Open bangtoven opened 9 years ago

bangtoven commented 9 years ago

I wonder when to commit and push the code regarding testing. Am I encouraged to commit each time whenever I make test code or actual code, or after real implementation is completed? How about pushing? Is there any guideline with it?

And in the case that I use stub or mocks because module of someone else was not finished yet, and later his/her part is ready, whose responsibility to make/edit the test code with actual module? Do I have to do? Or other person who finished the module have to do? Or (referring to 'I' in FIRST rule) no one's responsibility and leave it to integration testing? Or is there any automation tool which edit related test cases when new module is committed/pushed?

elnn commented 9 years ago

For the first question, it would be better to do commit early and often. Keep in mind that smaller atomic commits is good. I recommend you to see http://sethrobertson.github.io/GitBestPractices/