Difference between revisions of "Software Static Test Software Overview"

From HaFrWiki
Jump to: navigation, search
m (Coding Standards)
m (Coding Standards)
Line 17: Line 17:
  
 
=== CheckStyle ===
 
=== CheckStyle ===
See [[CheckStyle]] for a Maven Installation description.
+
See [[CheckStyle]] for an ANT and Maven Installation description for CheckStyle.
  
 
=== FindBugs ===
 
=== FindBugs ===

Revision as of 16:51, 15 August 2015

Static Test Software gives a measurable quality value (Metrics) of an existing software (development) project.

Introduction

Checking Tools do not make the software better. First of all make concrete engagements, appointments and agreements on how the software project will be made, which result in:

  • Compilation warnings rules and Lint (Language Interpreter) rules.
  • Coding Standards Rules.
  • Documentation Standards.
  • Unit Test and coverage percentage.
  • Deliverabeles

The Checking-Tools are the methods to verify the compliance to the agreements. This page only handles the static checking tools.

Compiler lint

The error and warning messages during the making of the software. Errors are in their nature not allowed, but also warnings may cause severe problems. How to cope with these kind of errors?

Coding Standards

CheckStyle

See CheckStyle for an ANT and Maven Installation description for CheckStyle.

FindBugs

See FindBugs

PMD

See PMD.

UnitTest

See jUnit and PhpUnit,



See also

top

Reference

top