Static Testing

Browse Lessons modules

1

Finding defects before execution

Requirements, user stories, designs, code, testware, contracts, and models can be examined without running the product. Static testing can find ambiguity, inconsistency, omissions, unreachable code, and violations of standards earlier and more cheaply.

Remember: You do not need executable software to begin testing.

2

A review process

A structured review commonly includes planning, review initiation, individual review, communication and analysis, and fixing and reporting. The formality and documentation should match risk, objectives, and organizational context.

Remember: A review is purposeful analysis, not merely reading a document.

3

Review roles and types

Authors create the work product, reviewers examine it, moderators facilitate, scribes record, and review leaders organize responsibility. Informal reviews, walkthroughs, technical reviews, and inspections differ in objectives, formality, leadership, and evidence.

Remember: Clear roles and an appropriate review type improve focus and accountability.

Learn together

Discussion & learner questions

Ask about a concept, share a practical example, or add context that may help another tester. ShiftQA reviews submissions before they become public.

Questions and comments stay distinct. Questions can receive an official ShiftQA response; comments support learner discussion and real-world examples.

Loading the discussion…

Save your progress

Finished this module?

Mark it complete in this browser, then continue when you are ready.

Unofficial ISTQB preparation by ShiftQA Labs. Use the official CTFL syllabus and sample materials as the source of truth.