About TestAcademy

TestAcademy teaches QA automation in your browser. You read a lecture, then you write real Cypress, Playwright or Selenium code against a real application and see if it passes. Nothing to install. There is also an AI mock interview that asks you questions the way an interviewer would.

Why I built it

My name is Art Shllaku. I am a QA Automation Engineer.

A few years ago, when I was preparing for interviews, I noticed something missing. There was no single place where I could actually practice the tools that keep showing up in job postings, Cypress, Playwright, Selenium, side by side, in one spot. Most sites teach you the syntax. Almost none of them let you write real code and see if it actually works.

So I decided to build the thing I wished existed when I was starting out.

What the official docs do not teach you

I have read the official docs for all three tools carefully, and I still read them. They are good. I link to them at the end of the lectures, and you should read them too: Playwright, Cypress and Selenium.

But documentation has one job. It tells you what a function does. It does not tell you which of five ways to do something is the right one for your team. It does not tell you why your test passes on your laptop and fails on the build server. It does not tell you what a reviewer will write on your pull request, or what an interviewer will ask you when you say you know Cypress.

That is the part I teach here. The docs hold the reference. This is where you learn the judgment, so that when you finish a track you can do the job and explain your choices, not only repeat the syntax.

Where the lessons come from

I work in testing, remotely, for international companies. I came to it from a frontend background, which is why I care about how an application is built and not only about how to click through it.

Some of what that has looked like. I led a migration of around 2,000 end to end tests from Cypress to Playwright, and cut flaky failures by about 15 percent. I took over an API suite of 918 tests and grew it past 2,100, covering functional, security and integration cases across four environments. I have been the only QA engineer on an enterprise platform used across a large organisation. I have led a small Cypress team. I have worked in regulated healthcare, where a bug is not only an inconvenience.

Every lesson, every practice problem, and every piece of feedback here comes from that work, not copied from documentation. I write and review the content myself, and I test it the way I would test any real application, by trying to break it first.

I wrote about testing before this, so you can see how I explain things before you pay for anything: Best E2E automation testing practices on Medium, and three more posts on my E2E Testing Hub.

How this is run

The Foundations track and the first lectures of every framework stay free, because I would rather you try the platform and judge it yourself before you decide it is worth paying for.

Payments are handled by Paddle, which is the registered seller for anything you buy here. If something is not what you expected, the refund policy explains what to do.

If you have feedback, something confusing, something wrong, something you wish existed, I want to hear about it. You are writing to me, not to a support queue. This platform gets better because people tell me what is missing.