For software developers, the Code Review process has been essential for ages, but they can also be used in software testing when you create test automation code.
Wikipedia defines code review as a systematic examination of computer source code to improve the overall quality of software. In his blog post, Joel Kemp provides some propositions on how to give better code reviews.
This presentation gives you a few code review tips for keeping your code healthy and your team happy. You will learn why talking about code in person is important, how to talk about code without burning bridges and, most importantly, how to take dread out of your workplace.
This presentation discusses problems and solutions that were made in solving problems such as size (about 100 people in total, more than 5 years long), multi-location (Vilnius, China, US), remote PO (teams in Eastern Europe, PO in US), ~550 000 LOC’s, multiple customers. It will present techniques used to maintain the project quality in shape: Continuous Integration, Code Review, Static Code Quality.
This post about exploratory testing and review discusses the misapprehension that the advocates of exploratory testing suggest that review or other forms of testing should be dropped.