3.1 Static testing basics

Question 1

What is static testing?

Answer 1

the software under test does not need to be executed.
Code, process specification, system architecture specification or other work products are evaluated
through manual examination (e.g., reviews) or with the help of a tool (e.g., static analysis)

Question 2

What are test objectives of static testing?

Answer 2

improving quality, detecting defects and assessing characteristics like readability, completeness,
correctness, testability and consistency. Static testing can be applied for both verification and validation

Question 3

Who collaborates during example mappings, collaborative user story writing, and backlog refinement sessions?

Answer 3

Testers, business representatives, and developers.

Question 4

What is the purpose of example mappings, collaborative user story writing, and backlog refinement sessions?

Answer 4

To ensure that user stories and related work products meet defined criteria, such as the Definition of Ready.

Question 5

What techniques can be applied to ensure user stories are complete and understandable?

Answer 5

review techniques

Question 6

What roles do testers play in the user story process?

Answer 6

testers, explore, challenge and help improve proposed user storied by asking the right questions

Question 7

What can static analysis identify prior to dynamic testing?

Answer 7

problems in the code
Evaluating maintainability and security

Question 8

Why does static analysis often require less effort than dynamic testing

Answer 8

because it does not require test cases and typically uses tools

Question 9

Into what frameworks is static analysis often incorporated?

Answer 9

continuous integration (CI) frameworks

Question 10

What are some examples of static analysis tools?

Answer 10

Spelling checkers and readability tools.

Question 11

What types of work products can be examined using static testing?

Answer 11

Requirement specification documents
source code
test plans
test cases
product backlog items
test charters
project documentation
contracts
models.

Question 12

Can any work product be the subject of a review?

Answer 12

Yes, any work product that can be read and understood can be the subject of a review.

Question 13

What is necessary for a work product to be suitable for static analysis?

Answer 13

The work product needs a structure against which it can be checked, such as models, code, or text with a formal syntax.

Question 14

What are examples of work products not appropriate for static testing?

Answer 14

Work products that are difficult to interpret by human beings and that should not be analyzed by tools, such as 3rd party executable code due to legal reasons.

Question 15

What principle does static testing fulfill by detecting defects in the earliest phases of the SDLC?

Answer 15

The principle of early testing.

Question 16

What types of defects can static testing identify that dynamic testing cannot?

Answer 16

Unreachable code, design patterns not implemented as desired, and defects in non-executable work products.

Question 17

What benefits does static testing provide in terms of work product quality and stakeholder confidence?

Answer 17

It allows evaluation of work product quality and builds confidence by verifying that documented requirements describe actual needs.

Question 18

How does static testing contribute to stakeholder understanding and communication?

Answer 18

By being performed early in the SDLC, it creates a shared understanding and improves communication among stakeholders.

Question 19

Why is it recommended to involve a wide variety of stakeholders in static testing?

Answer 19

To ensure a shared understanding and improved communication among the involved stakeholders.

Question 20

Despite the cost, why are reviews considered beneficial in the long run?

Answer 20

Because they reduce overall project costs by decreasing the time and effort needed to fix defects later in the project.

Question 21

How does static analysis compare to dynamic testing in terms of efficiency and development effort?

Answer 21

Static analysis detects code defects more efficiently, resulting in fewer code defects and a lower overall development effort.

Question 22

How do static testing and dynamic testing practices complement each other?

Answer 22

They have similar objectives, such as supporting defect detection in work products, but each can find certain types of defects the other cannot.

Question 23

What is a key difference between static testing and dynamic testing in terms of defect detection?

Answer 23

Static testing finds defects directly, while dynamic testing causes failures from which the associated defects are determined through subsequent analysis.

Question 24

Which type of testing is more effective for detecting defects on rarely executed paths in code?

Answer 24

Static testing.

Question 25

To what types of work products can static testing be applied?

Answer 25

Non-executable work products.

Question 26

To what types of work products can dynamic testing be applied?

Answer 26

Executable work products.

Question 27

What quality characteristics can static testing measure?

Answer 27

Quality characteristics not dependent on executing code, such as maintainability.

Question 28

What quality characteristics can dynamic testing measure?

Answer 28

Quality characteristics dependent on executing code, such as performance efficiency.

Question 29

Name types of defect in requirements that is easier and/or cheaper to find through static testing.

Answer 29

Inconsistencies
ambiguities
contradictions
omissions
inaccuracies
duplications

Question 30

Name design defects that is easier and/or cheaper to find through static testing.

Answer 30

Inefficient database structures, poor modularization

Question 31

Name types of coding defect that is easier and/or cheaper to find through static testing.

Answer 31

Variables with undefined values, undeclared variables, unreachable or duplicated code, excessive code complexity.

Question 32

What kind of deviation from standards is easier and/or cheaper to find through static testing?

Answer 32

Lack of adherence to naming conventions in coding standards.

Question 33

What kind of incorrect interface specification is easier and/or cheaper to find through static testing?

Answer 33

Mismatched number, type, or order of parameters.

Question 34

Name a type of security vulnerability that is easier and/or cheaper to find through static testing.

Answer 34

Buffer overflows

Question 35

What kind of gaps or inaccuracies in test basis coverage are easier and/or cheaper to find through static testing?

Answer 35

Missing tests for an acceptance criterion.