Chapter 3 - Static Testing

Question 1

In static testing, does the software under testing needs to be executed ? Eplain further what is static testing can do and how it can be applied.

Answer 1

No, code, process specification, system architecture specification or other work products are evaluated through manual examination or with the help of a tool (e.g., static analysis).
Static testing can be applied for both verification and validation.
It can also identify problems prior to dynamic testing while often requiring less effort, since no test cases are required and tools are typically used.

Question 2

Value of Static Testing ?

Answer 2

Static testing can detect defects in the earliest phases of the SDLC, fulfilling the principle of early testing.
It can also identify defects which cannot be detected by dynamic testing (e.g., unreachable code, design pattern not implemented as desired etc)
It provides the ability to evaluate the quality of, and to build confidence in work products. By doing that, the stakeholders can also make sure that these requirements describe their actual needs.

Question 3

Differencies between Static and Dynamic testing :

Answer 3

• can BOTH lead to the detection of defects, hoever some defect types can only be found by either static or dynamic testing.
• Static testing find defects directly, while dynamic testing causes failures whom which the associeted defects are derermined through subsequent analysis.
• Static testing may more easily detect defects that lay on paths through the code thar are rarely executed or hard to reach using dynamic testing
• Static testing can be applied to non-executable work products, while dynamic testing can only be applied to executable work products
• Static testing can be used to measure quality characteristics that are not dependent on executing code while dynamic testing can be used to measure quality characteristics that are dependent on executing code

Question 4

Typical defects that are easier and/or cheaper to find through static testing ?

Answer 4

• Defects in requirements (inconsistencies, ambiguities, omissions ..)
• Design defects (inefficient DB structures …)
• Certain types of coding defects (variables with undefined values, undeclared variables …)
• Deviations from standard (lack of adherence in naming standards …)
• Incorrect interface specs (mismatched number, type of order parameters …)
• Specific types of security vulnerabilities (buffer overflows …)
• Gaps or innacuracies in test basis coverage (missing tests for acceptance criterion …)

Question 5

Benefits of early and frequent Stakeholder feedback ?

Answer 5

Early and frequent feedback allows for the early communication of potential quality problems.
Frequent stakeholder feedback throughout the SDLC can prevent misunderstandings about requirements and ensure that changes to requirements are understood and implemented earlier.

Question 6

What are Review Process Activities ?

Answer 6

1. Planning
2. Review initiation
3. Individual review
4. Communication and analysis
5. Fixing and reporting

Question 7

Roles and Responsibilities in Reviews

Answer 7

1. Manager - desides what is to be reviewed and provides resources, such as staff and time for the review
2. Author - creates and fixes the work product under review
3. Moderator (facilitator) - ensures the effective running of review meetings, including mediation, time management, and safe review envorinment in which everyone can speak freely
4. Scribe (recorder) - collates anomalies from reviewers and records review information, such as decisions and new anomalies found during the review meeting
5. Review leader - takes overall responsibility for the review, such as deciding who will be involved and organizing when and where the review will take place

Question 8

Some commonly used Review types ? (4)

Answer 8

1. Informal view
2. Walkthrough
3. Technical review
4. Inspection

Question 9

Success Factors for Rewiews

Answer 9

• Defining clear objectives and measurable exit criteria
• Choosing the appropriate review type to achieve given objectives
• Conducting reviews on small chunks
• Providing feedback from reviewers to stakeholders
• Providing adequate time to participants to prepare for the review
• Support from management for the organisation’s culture
• Providing adequate training for all participants
• Facilitating meetings