QA fundamentals
Capstone: End-to-End Practice Release
A guided pretend release where you combine cases, exploration, and tickets under a published schedule with mentor review.
420,000 KRW · informational only
Inside the syllabus
You receive a staged build with seeded defects, plan coverage, execute, and file a concise release recommendation. Mentors comment on planning discipline and communication, not on finding every hidden bug.
What you practice
- Published schedule with realistic cutoffs
- Seed defects spanning UI, data, and copy
- Release recommendation template
- Mentor comments on planning and tone
- Optional retro with classmates
Outcomes you can describe aloud
- Deliver a coverage plan with explicit out-of-scope notes
- File a prioritized defect cluster with clean repro evidence
- Write a one-page release stance a lead could forward
Lead instructor
Builds practice labs, reviews submissions, and keeps lessons aligned with how junior testers work in real teams.
Questions people ask before enrolling
You receive narrative feedback, not letter grades. Employers never see scores.
Notes from people who sat where you sit
Release stance memo was harder than finding bugs. That was the point, and it showed.
Retro surfaced a communication habit I did not know I had—interrupting during debriefs.