Static Code Analysis

From Gcube Wiki
Revision as of 12:30, 15 January 2012 by Gabriele.giammatteo (Talk | contribs) (Created page with '__TOC__ Static Code Analysis is a testing methodology that tests software's source code, without actually running the program. Aspects checked by static analysis are: syntax cor…')

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents

Static Code Analysis is a testing methodology that tests software's source code, without actually running the program. Aspects checked by static analysis are: syntax correctness of source code, compliance with formatting guidelines, correctness of algorithms, probable bugs, presence of a proper code documentation.


gCube System exploits the ETICS building tool to carry out static analysis of code. Indeed, ETICS System offers to its users the capability of running a large set of static code analysis tools during ETICS builds. This is made possible by the ETICS plugin mechanism: users choose the set of plugins to run during builds of their project and ETICS will run those plugins at every build; reports of plugins executions will be made available along with other build reports. In particular, gCube project in ETICS is configured to run two famous static code analysis tools for java software:


Checkstyle

Checkstyle is one of the most famous java code analysis tool. It is capable of checking

Retrieved from "https://gcube.wiki.gcube-system.org/index.php?title=Static_Code_Analysis&oldid=13027"