Session 1.7 - Testing Terminology & Methodology
Module 1: Introduction to Software Testing | Duration: 1 hour
Learning Objectives
- Establish a shared glossary for professional testing.
- Differentiate testing levels, approaches, and artifacts.
- Relate methodologies (Agile/DevOps) to day-to-day testing workflows.
Glossary: Core Terms
Defect / Bug / Fault: A flaw that can cause failure.
Failure: Deviation of delivered service from expected result.
Error: Human action producing an incorrect result.
Test Case: Inputs, execution conditions, and expected results.
Test Suite: A set of test cases grouped for execution.
Test Plan / Strategy: Scope, approach, resources, and schedule.
Test Oracle: Source of expected outcomes (specs, contracts, heuristics).
Test Environment: Hardware, software, data, and network setup.
Testing Levels
Unit: Validate smallest testable parts (functions/classes).
Integration: Verify interfaces and collaborations among components.
System: Validate end-to-end behavior in realistic environments.
Acceptance: Confirm product meets user/business needs.
Approaches & Techniques
- Black-box: EC, BVA, decision tables, state-based, use cases.
- White-box: Control/data flow, branch/path, mutation.
- Grey-box: Combine interface knowledge with internal hints.
- Non-functional: Performance, security, usability, reliability.
Artifacts & Workflow
- Plan → Design → Implement → Execute → Report → Improve.
- Artifacts: plan, strategy, cases, data, scripts, reports, dashboards.
- Traceability from requirements to tests to defects to releases.
Methodologies & Process Models
Agile: Tests embedded in stories (DoD), frequent increments, continuous feedback.
DevOps: Continuous testing in CI/CD, shift-left & shift-right (observability-driven).
Shift-left: Early involvement in requirements/design, contract tests.
Shift-right: Synthetic monitoring, canary checks, chaos, and resiliency testing.
Roles & Collaboration
- QA / Tester: Scenario design, exploratory, risk articulation.
- SDET: Test frameworks, automation, CI integrations.
- Developers: Unit tests, code reviews, contract tests.
- PO/UX/Ops: Acceptance criteria, usability, operability.
Summary & Assignment
Terminology clarity plus the right methodology unlocks reliable, efficient testing practices that scale with team and product complexity.
Assignment: Create a one-page testing glossary for your team and map each term to where it appears in your workflow (artifact, tool, or meeting).