You may have hit that issue in a college project or other hobby project you did with others. You wrote a certain class or a module and a few weeks later, a colleague tries to update it and he tries to update the names or the style of the code. You may have engaged in […]
I have seen thousands of code reviews. A good code review happens when both the developer and the reviewer follow a productive etiquette: Always remember that code reviews are not competitions and shouldn’t turn into fights. Avoid being aggressive in your comments or responses. You work with the person on the other end. Be respectful […]
Once you implement a feature and before you commit the code to the source code system it is common to have the code reviewed by your teammates. The goal of the code review is to make sure that the code meets the expectations of functionality, design, test coverage, and style. On functionality, the reviewer should […]
One mistake I see many people make is relying on internal details in their tests. For example, assume that you wrote a stack class and that you use an array to store the data. This should be an internal matter for your class. You should not write a test case that verifies the order of […]
Design is a process that results in a document called the Design Document. The document should provide several key sections covering core areas of the design process. The process starts with a problem that needs a solution. Your first goal as a designer is to make sure that you understand the problem, so you need […]
As you design and maintain tests for your system, keep the following points in your mind: Ease of use and debugging are the highest priority. Everyone on the team should be able to run and debug the tests. Use your creativity to make the tests easy to run and debug instead of focusing on the most […]