Overview of software testing
The importance of Quality Assurance and Testing
Roles in testing
Practice
Assignment
Tester Track
Roles in Testing
Testing includes different responsibilities, and quality is not owned by only one person.
Test management role
The test management role focuses on planning, coordination, monitoring, and reporting.
Typical responsibilities include:
- defining test scope
- prioritizing testing activities
- managing risks
- tracking progress
- reporting test status
- supporting release decisions
Testing role
The testing role focuses more on analysis and execution.
Typical responsibilities include:
- reviewing requirements
- designing tests
- preparing test data
- executing tests
- reporting defects
- verifying fixes
- supporting regression testing
In smaller teams, one person may perform both management and testing activities.
Whole team approach
Testing is not only the tester's responsibility. Quality is a shared responsibility across the whole team.
For example:
- product managers help clarify requirements
- developers support code quality, unit testing, and defect fixing
- testers provide product evaluation and risk feedback
- designers, analysts, and other stakeholders may help validate usability and business flows
Independence of testing
Testing is often more effective when there is some independence.
Why this matters:
- people may miss defects in their own work
- an independent perspective can challenge assumptions
- a fresh reviewer or tester may notice risks others missed
Independence can exist at different levels:
- developers testing their own code
- another developer reviewing or testing the feature
- a dedicated tester testing the feature
- an independent or external test team
Key takeaway: Quality is everyone's responsibility, but independent testing still adds valuable perspective.
Self-check
- What is the difference between a test management role and a testing role?
- Why is testing considered a whole team activity?
8. How this looks in real QA work
In real projects, testing is not limited to executing test cases. A tester may:
- review requirements and identify risks
- ask clarifying questions
- design test cases or checklists
- perform static and dynamic testing
- report failures and defects
- verify fixes
- support regression testing
- share quality feedback before release
A QA-minded team may also:
- improve workflows
- reduce avoidable defects
- learn from incidents
- strengthen communication between product, development, and testing
Key takeaway: Testing is part of daily product work, not a final step that happens only at the end.
Summary
| Concept |
Summary |
| Software testing |
Activities used to evaluate quality and identify important defects and risks |
| Testing vs debugging |
Testing finds problems, debugging finds causes and fixes them |
| Contribution to success |
Testing reduces risk, supports decisions, and helps avoid costly failures |
| Error / defect / failure/ root cause |
Problems often start with a human mistake and may end with visible failure unless caught early |
| Quality Assurance |
Process-oriented work aimed at defect prevention and quality improvement |
| Seven principles |
Testing has limits, depends on context, and must be prioritized |
| Roles in testing |
Quality is a whole team responsibility, but independent testing remains valuable |
Mini glossary
- Static testing: evaluating work products without running software
- Dynamic testing: evaluating software by running it
- Error: human mistake
- Defect: flaw in a work product
- Failure: incorrect behavior during execution
- Root cause: underlying reason for a problem
- Testing: product-focused quality evaluation activity
- Debugging: investigation and fixing of defects
- Quality Assurance: process-oriented activities to prevent defects
Further reading:
- ISTQB Certified Tester Foundation Level syllabus — istqb.org
- Ministry of Testing — ministryoftesting.com
- Articles and case studies about real software failures