A 12-week live course in game testing and QA. You will test real builds, file real bug reports, and finish with a portfolio you can put in front of a studio.
Resolution: build the commercial experience first — real builds, real test suites, real reports. That is what this course is.
Playing a game and testing one are different activities. Studios hire people who can do the second.
Work from design documents to build test suites that cover a feature properly, including the edge cases nobody thought about. Structured coverage beats wandering around hoping something breaks.
Narrow a vague crash into exact, repeatable steps. This is the skill that decides whether a bug gets fixed this sprint or sits in the backlog marked unreproducible.
Write it up so a developer who has never seen the problem can reproduce it in a minute. Clear severity, clean repro, the right logs and captures attached.
Each one answers a different question about the build, and each has its own tools and habits.
Does the game do what the design document says it does?
Does it run properly on the hardware players actually own?
Did this week's fix break something that worked last week?
Does it hold frame rate, and does it survive eight hours running?
Does the game read correctly in every language it ships in?
Will the platform holder actually let the game ship?
Does it hold together when the connection does not?
The game works. Is it understandable, and is it any good?
Three steps, and you keep your place as soon as the fee clears.
Name, contact details and a little about your background, so we know who is joining.
We send a link to the address you gave. Clicking it confirms the address is real and yours.
The confirmation link takes you straight to secure payment. Your seat is held once it clears.
No. Game testing is not a programming job. You need to be observant, systematic and able to write clearly. We cover the small amount of scripting used in automated regression work, starting from zero.
Plan for about ten hours: two live sessions of ninety minutes, plus testing assignments on real builds. Sessions are recorded if you cannot attend live.
Online and live. Sessions run in the evening so you can study alongside a job or college.
A computer that can run current games, a stable internet connection and a headset. A controller is useful but not required.
No course can promise a job, and you should be sceptical of any that does. What we can do is make you employable: a portfolio of real bug reports, a working knowledge of what studios test for, and practice with the exercises QA interviews actually use.
Register, confirm your email address, and you are taken straight to a secure payment page. Payments are handled by Razorpay. Cards, UPI, net banking and wallets are all accepted.
Register now, confirm your email, and pay when you are ready. Places are limited so that every student gets reviewed on their bug reports.
