Static software test procedure

from Wikipedia, the free encyclopedia

Static software test procedures (short: static tests ) belong to the analyzing procedures in software tests and are divided into

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

Static software test procedures are characterized by the fact that the software is not executed in these tests ( non-execution based methods ), in contrast to dynamic software test procedures ( execution based methods ).

Software reviews

Reviews use human thinking and analysis skills to check the test object through reading and understanding. The IEEE 1028 standard ( Standard for Software Reviews and Audits ) describes five types of reviews :

  • Management review
  • Technical review
  • Walkthrough
  • Inspection
  • Audit

These review types can in principle be applied to all work results in the software development process (e.g. requirements specifications , design specifications , source code , test specifications , software documentation ) and thus offer the possibility of implementing quality assurance measures very early on in the software development phase. Participants in such a review are at least the author of the program, an expert, a note-taker and a moderator. A standardized checklist is often used. With the help of a full review, 60–90% of errors are found. The walkthrough is a variant with less formal effort and fewer participants.

Exemplary checklist

  1. Functional scope / specification / draft / documentation
    Has the function been implemented according to the specification?
    Is the documentation for the program available and complete?
    Does the program not contain the desired / specified code?
    ...
  2. Programming in general
    Is there code that exists more than once (e.g. through multiple copying)
    ...
  3. Initialization and declaration
  4. Method call
  5. Fields
  6. ...

Static analysis

The static analysis aims to find errors in the program code or in formally described software models. The static analysis is carried out with the appropriate tool support. Static analysis tools can be used for checking against programming guidelines, data flow analysis, control flow analysis and the creation of metrics (e.g. lines of code (LOC), cyclomatic complexity ).

Individual evidence

  1. ^ Institute of Electrical and Electronics Engineers: 1028-2008 - IEEE Standard for Software Reviews and Audits . Institute of Electrical and Electronics Engineers, New York 2008, ISBN 978-0-7381-5769-6 , doi : 10.1109 / IEEESTD.2008.4601584 .

literature

  • Andreas Spillner, Theo Linz: Basic knowledge of software testing. Training and further education to become a Certified Tester . Foundation level according to the ISTQB standard. dpunkt-Verlag, Heidelberg, ISBN 3-89864-358-1 .
  • Peter Liggesmeyer : Software quality. Testing, analyzing and verifying software . Spectrum Academic Publishing House, Heidelberg / Berlin 2002, ISBN 3-8274-1118-1 .
  • Harry Sneed , Richard Seidl , Manfred Baumgartner: Software in numbers. The measurement of applications . 1st edition. Carl Hanser, Munich 2010, ISBN 978-3-446-42175-2 .

Web links