Software Static Test Software Overview

From HaFrWiki
Revision as of 17:39, 15 August 2015 by Hjmf (talk | contribs) (Coding Standards)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Access-rights violation
The requested action is not allowed by this wiki website.
See the description below for detailed information.

Detailed Access-rights violation
The requested action has been read access for ⧼wikirbac-title-page (history-access)⧽ Software Static Test Software Overview.
The webmaster/administrator has restricted access to this information using the Role Based Access Control (RBAC).
An entry of this violation has been created in the Log-file with timestamp 19 September 2019 09:05:00.
Details access limitation.
  • No-Super-UserGroup 4 All Categories.
  • No-Super-UserGroup 4 All Categories.
  • Restriction for all usergroups's (*) found for cat Index.
  • No access credentials found for Access: History



RBAC-Documentation
See the the website documentation (HaFrWikiCommunity Portal) for more information.

Suggested continuation

Return to Main Page.

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

Introduction[edit]

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[edit]

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[edit]

CheckStyle[edit]

Checkstyle is a development tool to help programmers write Java code that adheres to a coding standard. It automates the process of checking Java code to spare humans of this boring (but important) task. This makes it ideal for projects that want to enforce a coding standard.

Checkstyle is highly configurable and can be made to support almost any coding standard. An example configuration files are supplied supporting the Sun Code Conventions, Google Java Style.

See CheckStyle for an Ant and Maven installation description for CheckStyle.

FindBugs[edit]

FindBugs is a program which uses static analysis to look for bugs in Java code. It is free software, distributed under the terms of the Lesser GNU Public License. The name FindBugs™ and the FindBugs logo are trademarked by The University of Maryland. FindBugs has been downloaded more than a million times.

See FindBugs for an Ant installation description for FindBugs.

PMD[edit]

See PMD.

UnitTest[edit]

See jUnit and PhpUnit,



See also[edit]

top

Reference[edit]

top