<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Software testing code review tutorials and videos</title>
	<atom:link href="https://www.softwaretestingmagazine.com/tag/code-review/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.softwaretestingmagazine.com</link>
	<description></description>
	<lastBuildDate>Mon, 17 Nov 2025 18:02:19 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://www.softwaretestingmagazine.com/wp-content/uploads/favicon.png</url>
	<title>Software testing code review tutorials and videos</title>
	<link>https://www.softwaretestingmagazine.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Lessons Learned From Code Review Remarks</title>
		<link>https://www.softwaretestingmagazine.com/videos/lessons-learned-from-code-review-remarks/</link>
					<comments>https://www.softwaretestingmagazine.com/videos/lessons-learned-from-code-review-remarks/#comments</comments>
		
		<dc:creator><![CDATA[Software Testing Magazine]]></dc:creator>
		<pubDate>Tue, 21 Oct 2025 20:05:33 +0000</pubDate>
				<category><![CDATA[Software Testing Videos]]></category>
		<category><![CDATA[code review]]></category>
		<category><![CDATA[software quality assurance]]></category>
		<guid isPermaLink="false">https://www.softwaretestingmagazine.com/?p=10710</guid>

					<description><![CDATA[<p>It appears that one consequence of being a tech lead is that team members consider you the default reviewer for all their pull requests (PR). Though the code review process seems straightforward, there are many aspects that need to be considered. Effectively being one form of feedback, I would like to share my observations and give advice to future leaders about making this process as smooth as possible. Code review is an essential technique to improve the code quality and share knowledge. It helps developers grow, opens space for constructive criticism and discussions. This presentation shares general guidance about how to approach reviewing PRs based on size and complexity. Then, the main focus is about the soft skills related to code revies, targeting the following questions: Do I need to tailor review per team member? How will the written feedback be interpreted? How detailed should feedback be? What actions to take if you want to decrease the amount of remarks in a PR? Many of these situations are based on personal experience from making code review for more than 8 years. Video producer: https://www.devoxx.com/ Further readings Google guide: How to do a code review How to review code effectively: A GitHub staff engineer’s philosophy Code Review: Why It Matters</p>
The post <a href="https://www.softwaretestingmagazine.com/videos/lessons-learned-from-code-review-remarks/">Lessons Learned From Code Review Remarks</a> first appeared on <a href="https://www.softwaretestingmagazine.com">Software Testing Magazine</a>.]]></description>
		
					<wfw:commentRss>https://www.softwaretestingmagazine.com/videos/lessons-learned-from-code-review-remarks/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Code Reviews for Test Automation Code</title>
		<link>https://www.softwaretestingmagazine.com/videos/code-reviews-for-test-automation-code/</link>
		
		<dc:creator><![CDATA[Software Testing Magazine]]></dc:creator>
		<pubDate>Wed, 18 Jan 2017 14:04:04 +0000</pubDate>
				<category><![CDATA[Software Testing Videos]]></category>
		<category><![CDATA[code review]]></category>
		<category><![CDATA[test automation]]></category>
		<guid isPermaLink="false">http://www.softwaretestingmagazine.com/?p=5128</guid>

					<description><![CDATA[<p>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. It has been proven that it detects more bugs than any other form of testing, improves code quality, fosters knowledge sharing (for both the reviewer and the developer) and is cost effective. Code review can also be used successfully in Test Automation which will strengthen the collaboration between technical and functional specialists (Developers and QA). I will present our techniques for Test Automation Code Review; although it’s not the entire recipe, following them is an ingredient for better test code (clean, readable, simple, robust, bug free, extendable…). Video producer: http://www.testcon.lt/</p>
The post <a href="https://www.softwaretestingmagazine.com/videos/code-reviews-for-test-automation-code/">Code Reviews for Test Automation Code</a> first appeared on <a href="https://www.softwaretestingmagazine.com">Software Testing Magazine</a>.]]></description>
		
		
		
			</item>
		<item>
		<title>How to Give Better Code Reviews</title>
		<link>https://www.softwaretestingmagazine.com/knowledge/how-to-give-better-code-reviews/</link>
		
		<dc:creator><![CDATA[Software Testing Magazine]]></dc:creator>
		<pubDate>Mon, 24 Oct 2016 15:14:45 +0000</pubDate>
				<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[Software Testing Blogs]]></category>
		<category><![CDATA[code review]]></category>
		<guid isPermaLink="false">http://www.softwaretestingmagazine.com/?p=4838</guid>

					<description><![CDATA[<p>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. Joel Kemp starts hist by explaining that code reviews are a key tool create knowledge transfer and spread best practices throughout a development team. There are at least two phases in code reviews and most people stop at the first and less valuable phase where only the obvious issues are examined. The second phase is the contextual pass where participants examine issues like adequate usage of frameworks/libraries or a satisfactory test coverage. During this phase, Joel Kemp advice to be cautious of how you ask questions: you should suggest approaches or provoke exploration and not try to deliver solutions. The conclusion of the post is that &#8220;[&#8230;] reviewing code is as much of a craft as writing code. As reviewers, it’s our mission to improve on a number of fronts: our ability to understand code; our process, awareness, and criteria for analysis; and our teammates’ ability to write correct diffs.&#8221; Read the complete blog post on https://medium.com/@mrjoelkemp/giving-better-code-reviews-16109e0fdd36</p>
The post <a href="https://www.softwaretestingmagazine.com/knowledge/how-to-give-better-code-reviews/">How to Give Better Code Reviews</a> first appeared on <a href="https://www.softwaretestingmagazine.com">Software Testing Magazine</a>.]]></description>
		
		
		
			</item>
		<item>
		<title>Better Code Reviews</title>
		<link>https://www.softwaretestingmagazine.com/videos/better-code-reviews/</link>
		
		<dc:creator><![CDATA[Software Testing Magazine]]></dc:creator>
		<pubDate>Tue, 27 Jan 2015 17:21:53 +0000</pubDate>
				<category><![CDATA[Software Testing Videos]]></category>
		<category><![CDATA[code review]]></category>
		<guid isPermaLink="false">http://www.softwaretestingmagazine.com/?p=3500</guid>

					<description><![CDATA[<p>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. Event: Forward JS Video producer: https://thenewcircle.com/ Further reading: Four Ways to a Practical Code Review</p>
The post <a href="https://www.softwaretestingmagazine.com/videos/better-code-reviews/">Better Code Reviews</a> first appeared on <a href="https://www.softwaretestingmagazine.com">Software Testing Magazine</a>.]]></description>
		
		
		
			</item>
		<item>
		<title>Chasing Code Quality in a Distributed Team</title>
		<link>https://www.softwaretestingmagazine.com/videos/chasing-code-quality-in-a-distributed-team/</link>
		
		<dc:creator><![CDATA[Software Testing Magazine]]></dc:creator>
		<pubDate>Thu, 20 Dec 2012 21:20:32 +0000</pubDate>
				<category><![CDATA[Software Testing Videos]]></category>
		<category><![CDATA[code analysis]]></category>
		<category><![CDATA[code review]]></category>
		<category><![CDATA[continuous integration]]></category>
		<guid isPermaLink="false">http://www.softwaretestingmagazine.com/?p=1960</guid>

					<description><![CDATA[<p>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&#8217;s, multiple customers. It will present techniques used to maintain the project quality in shape: Continuous Integration, Code Review, Static Code Quality. Event: Agile Tour Lithuania</p>
The post <a href="https://www.softwaretestingmagazine.com/videos/chasing-code-quality-in-a-distributed-team/">Chasing Code Quality in a Distributed Team</a> first appeared on <a href="https://www.softwaretestingmagazine.com">Software Testing Magazine</a>.]]></description>
		
		
		
			</item>
		<item>
		<title>Exploratory Testing and Review</title>
		<link>https://www.softwaretestingmagazine.com/knowledge/exploratory-testing-and-review/</link>
		
		<dc:creator><![CDATA[Software Testing Magazine]]></dc:creator>
		<pubDate>Fri, 24 Sep 2010 11:08:03 +0000</pubDate>
				<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[Software Testing Blogs]]></category>
		<category><![CDATA[code review]]></category>
		<category><![CDATA[exploratory testing]]></category>
		<guid isPermaLink="false">http://www.softwaretestingmagazine.com/?p=307</guid>

					<description><![CDATA[<p>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.</p>
The post <a href="https://www.softwaretestingmagazine.com/knowledge/exploratory-testing-and-review/">Exploratory Testing and Review</a> first appeared on <a href="https://www.softwaretestingmagazine.com">Software Testing Magazine</a>.]]></description>
		
		
		
			</item>
	</channel>
</rss>
