Content deleted Content added
m Reverted edits by 62.7.89.150 (talk) (HG) (3.4.13) |
m →Overview: HTTP to HTTPS for SourceForge |
||
Line 7:
Some [[static code analysis]] tools can be used to help with automated code review. They do not compare favorably to manual reviews, however they can be done faster and more efficiently.{{Citation needed|date=January 2018|reason=Need evidence that manual reviews are better than automated}} These tools also encapsulate deep knowledge of underlying rules and semantics required to perform this type analysis such that it does not require the human code reviewer to have the same level of expertise as an expert human auditor.<ref name="SA_ref"/> Many [[Integrated Development Environments]] also provide basic automated code review functionality. For example the [[Eclipse (software)|Eclipse]]<ref>{{cite web|title=Collaborative Code Review Tool Development |publisher=www.eclipse.org |url=http://marketplace.eclipse.org/content/collaborative-code-review-tool |accessdate=2010-10-13 |url-status=dead |archiveurl=https://web.archive.org/web/20100401051935/http://marketplace.eclipse.org/content/collaborative-code-review-tool |archivedate=2010-04-01 }}</ref> and [[Microsoft Visual Studio]]<ref>{{cite web|title=Code Review Plug-in for Visual Studio 2008, ReviewPal | date=4 November 2009 | publisher=www.codeproject.com | url=http://www.codeproject.com/KB/work/ReviewPal.aspx | accessdate=2010-10-13}}</ref> IDEs support a variety of plugins that facilitate code review.
Next to [[static code analysis]] tools, there are also tools that analyze and [[Software visualization|visualize software structures]] and help humans to better understand these. Such systems are geared more to analysis because they typically do not contain a predefined set of rules to check software against. Some of these tools (e.g. [[Imagix 4D]], [[Resharper]], [[SonarJ]], Sotoarc, [[Structure101]], ACTool<ref>[
==Automated code review tools==
| |||