Code Review
Systematic examination of code by other developers before it is merged into the main branch.
Code review refers to the examination of a code change by at least one other person before it is adopted into the shared main branch. This is usually done through a pull or merge request: the proposed changes are commented on, questions are asked and adjustments are requested before the merge is approved.
What is checked is not only obvious errors, but also readability, architectural decisions and the question of whether a change fits into the existing code. A code review spreads knowledge in the team and lowers the probability that a single blind spot goes undiscovered.
What Provimedia uses it for
Provimedia has every change to shared code reviewed by colleagues and puts Code Guardian in front of that as an additional, automated layer.
Want to use Code Review for your project?
In a free conversation, let's find out how we can implement this for you.
More from Software quality
Clean Code
Guiding idea for code that is designed to be understandable for humans and not just for the compiler.
Learn moreCode Smell
Conspicuous pattern in code that is not necessarily wrong but points to a deeper problem.
Learn moreDefinition of Done
Written list of criteria agreed in the team that a task must meet in order to count as done.
Learn moreLinting
Automated checking of code for style and formatting errors according to fixed rules.
Learn moreMutation Testing
Technique that deliberately introduces small errors into the code to check how meaningful the tests are.
Learn moreQuality Gate
Check stage in the development pipeline that lets a change pass only if fixed criteria are met.
Learn moreRefactoring
Targeted restructuring of existing code without changing its external behavior.
Learn moreRegression Test
Re-testing of existing functions after a change in order to detect newly introduced errors.
Learn more