Software Static Test Software Overview: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
|||
| Line 17: | Line 17: | ||
=== CheckStyle === | === CheckStyle === | ||
See [[CheckStyle]] | See [[CheckStyle]] for a Maven Installation description. | ||
=== FindBugs === | === FindBugs === | ||
| Line 23: | Line 23: | ||
=== PMD === | === PMD === | ||
See [[PMD]]. | See [[PMD]]. | ||
==UnitTest == | ==UnitTest == | ||
Revision as of 11:07, 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 a Maven Installation description.
FindBugs
See FindBugs
PMD
See PMD.
UnitTest