Code review
Focused examination of a source change for design, behaviour, clarity and appropriate checks.
Understand a change’s behaviour
A code review examines a source change deliberately. This includes design, intended behaviour, clarity and suitable tests. Automated findings can help; formatting checks alone do not answer functional questions.
In a fictional example, a report’s date display changes. The reviewer also considers missing dates and whether tests cover this important case. A visible change may require execution or demonstration to assess its effect. Record significant findings and their resolution. A review replaces neither all runtime tests nor evidence of a complete user workflow. Personal style preferences should be distinguished from reasoned problems.
Sources
Related terms
- CommitA recorded project state with metadata and, where applicable, links to earlier states in Git.
- Pull requestA proposal to integrate changes into a target branch, with context for shared review and discussion.
- Contract testA test of agreed messages between a consumer and a provider at an application interface.
- Legacy systemAn existing system still in use, with technical and business dependencies accumulated over time.
- Multi-tenancyMulti-tenancy supports separate customer or group scopes in one solution. A tenant is not automatically one person or one database.
- Browser cacheThe browser cache stores suitable HTTP responses for later use. Reuse and revalidation follow the applicable rules.
Articles on this topic
Software Development with ASES
Custom software, web and mobile apps