3.1 Static Testing Basics

Question 1

In static testing, the software under test doesn’t need to be “ “.

Answer 1

executed

Question 2

Code, process specification, system architecture specification or other work products are evaluated through m… or with the help of a t…

Answer 2

manual examination (e.g. reviews)

tool (e.g. static analysis).

Question 3

Static testing
Test objectives include:
- imp…
- det…
- ass…
- “rea…”
- “com…”
- “cor…”
- “tes…”
- “con…”

Answer 3

• improving quality
• detecting defects
• assessing characteristics like
  
  • readability
  • completeness
  • correctness
  • testability
  • consistency.

Question 4

Static testing can be applied for both v…

Answer 4

verification and validation.

Question 5

Testers, business representatives (Product Owner, business analyst etc.) and developers work together during:
- example m…
- collaborative user s…
- backlog refine… to ensure that u… and r… meet d… e.g the D…

Answer 5

• example mapping
• collaborative user story writing
• backlog refinement sessions
  user stories
  related work products
  defined criteria,
  Definition of Ready.

Question 6

Review techniques can be applied to ensure u… are “c…“ and “ “ and include t…

By asking the right questions, testers “e…“, “ “, and help improve the p…

Answer 6

user stories
complete
understandable
testable acceptance criteria.

explore
challenge
proposed user stories.

Question 7

Static analysis can identify “ “ prior to d… while often requiring less “ “ since no t… are required, and tools are t…

Static analysis is often “ “ into C…

Answer 7

problems
dynamic testing
effort
test cases
typically used.

incorporated
CI frameworks.

Question 8

While largely used to detect specific code defects, static analysis is also used to evaluate “m…“ and “ “.

Spell checkers and readability tools are other “ “ of s…

Answer 8

maintainability
security

examples
static analysis tools.