Static testing

Static software testing process ( briefly: static tests ) are among the analyzed method with the software test and can be divided into

• Structured group testing (English review )
• Static code analysis or short static analysis

Static software test processes are characterized by the fact that the software is not running in these tests (non- execution based methods ), as opposed to dynamic software testing process ( execution based methods ).

Software Reviews

In Reviews one uses the human thinking and analysis skills to test by reading and understanding the test object. The IEEE 1028 (Standard for Software Reviews and Audits ) describes five types of review:

• Management Review
• Technical Review
• Walkthrough
• Inspection
• Audit

These types of reviews can in principle on all work results in the software development process (eg requirements specifications, design specifications, source code, test specifications, software documentation) are applied and thus offer the possibility of very early perform quality assurance measures in the software development phase. Participants of such reviews are at least the author of the program, an appraiser, a secretary and a moderator. Often a standard checklist is used. With the help of a complete Reviews 60-90 % of the errors are found. The Walkthrough is a variant with less effort and less formalistic participants.

Exemplary Checklist

Static Analysis

The static analysis to find the target, errors in the program code or software described in formal models. The static analysis is carried out with appropriate tool support. Applications of static analysis tools is to check against coding standards, data flow analysis, control flow analysis and compilation of metrics (eg lines of code (LOC ), cyclomatic complexity).