teamwork - Teamworking in software development etiquette -
I use a lot of coding (when lucky enough to assign something ...) are usually personal projects As I run source control only locally, what are the best practices for working with source control and generally working in software development team? Etiquette, best practices, what not to do etc.
Always store your source control trunk in the compilation state - this means that you will never have to compile errors Should not be checked in code with
What I usually do is write a script that is capable of running a test, and only checks it after running it. This script is clean compile and then runs all the unit tests / system tests and verifies the correctness, there is also a regression test, which remains in this way to show everything working in the beginning.
In addition, as often as possible check-ins, you can rollback in almost every possible situation. In addition, for the same reason, write informative comments while checking.
Comments
Post a Comment