I’m starting my journey into Quality Assurance (QA).
And honestly, I’m starting from the beginning.
I want to understand how software is tested, how bugs are found, how quality is maintained, and what it really means to work as a QA tester.
Why QA?
Software is everywhere.
But good software isn't just about building features. It’s also about making sure those features work as expected.
Hence, QA.
I’m interested in learning how testers think:
- What can go wrong?
- How can I find it?
- How do I know the software is working correctly?
- How do I communicate a problem clearly?
- How can testing help build better software?
Why now?
Because I don't want to keep waiting until I feel ready.
I have decided to learn by doing and document the journey as I go.
I won't pretend to be an expert.
I will learn something → practice it → make mistakes → fix them → write about it.
Hopefully, someone starting their own QA journey can learn alongside me.
The Road Ahead
I will start with Manual QA and gradually move toward automation.
My roadmap looks something like this:
- Manual QA
- Testing Fundamentals
- Test Cases & Bug Reporting
- API Testing
- Test Automation
- Real Projects QA Job Ready
I will document the things I learn, the things I struggle with, and the things that finally make sense.
Day 1 Starts Here
This is not a story about becoming an expert.
It's the beginning of a journey.
I'm learning QA and I'm taking you with me.
Next up:
What exactly is QA, and what does a QA tester actually do?
