My first note:
Software Quality Assurance vs Software Testing
What is Quality Assurance (QA)?
Software Quality Assurance (QA) is about improving the process used to build software so that quality is built in from the start.
It looks at the bigger picture — processes, requirements, development, testing, and how the team works.
What is Testing?
Software testing is about checking the actual software to find problems and verify that it behaves as expected.
For example:
A developer builds a login page.
A tester checks:
- Can a user log in with valid credentials?
- What happens with the wrong password?
- What if the email is empty?
- What if the password is empty?
- What happens after several failed attempts?
These checks can reveal defects before users do.
QA vs Testing
| QA | Testing |
|---|---|
| Prevents quality problems | Finds problems |
| Process-focused | Product-focused |
| Starts early | Happens throughout development |
| Asks “How can we prevent defects?” | Asks “Can we find defects?” |
They are different, but they work together.
What does a QA tester actually do?
A QA tester does not simply click around looking for bugs.
They:
- Understand requirements
- Think about what could go wrong
- Design test cases
- Execute tests
- Report defects
- Retest fixes
- Perform regression testing
- Explore the software
- Communicate with developers and other team members
And perhaps most importantly:
They think like the user, and sometimes like the person trying to break the software.
QA is about helping teams build better software and not just only finding bugs.
I'm learning QA and I'm taking you with me.
Top comments (1)
lets go😅