QA fundamentals
Foundations of Manual QA
A calm first pass through environments, builds, and how testers read risk before opening a single ticket.
129,000 KRW · informational only
Inside the syllabus
You learn how software reaches testers, what “ready for review” means without hype, and how to keep notes that help developers reproduce issues. The week ends with a small exploratory session on a sample shopping flow where you practice pausing, documenting, and asking better questions.
What you practice
- Readable checklists you can reuse on the next build
- Short drills on repro steps and evidence capture
- Glossary cards for jargon-heavy release notes
- A simple quality standards map for your portfolio
- Office-hour prompts so you know what to ask mentors
Outcomes you can describe aloud
- Describe a release candidate using neutral, precise language
- Produce a clean repro outline for a UI defect
- Choose the right artifact (screens, logs, HAR) without oversharing
Lead instructor
Builds practice labs, reviews submissions, and keeps lessons aligned with how junior testers work in real teams.
Questions people ask before enrolling
No. You should be comfortable installing desktop browsers and following written steps. We do not teach programming in this module.
Notes from people who sat where you sit
The repro template from week two is now pinned in my notes app. I liked that the examples were small retail flows, not giant enterprise screens.
Clear pacing, though I wanted one more audio-only walkthrough for commuters.