faq

Questions, answered

Learn what to expect before you start.

What is TestAcademy?+
TestAcademy helps you practise browser testing. Read the tutorials, then write and run tests in the practice editor. Use Playwright, Cypress or Selenium in your browser. The interview preparation includes questions and coding tasks by role.
Do I need to install anything?+
No installation is needed for the practice editor. The editor, practice app and tests run in your browser. Use a laptop or desktop so the editor has enough room. Some article downloads run on your computer and have their own setup instructions.
Does this run the real Playwright, Cypress and Selenium?+
The editor uses a browser runner, not the full framework packages. It supports a limited set of commands from each framework. You can find elements, use the page and check results. It also supports automatic waits and assertions that retry. Network interception, multiple tabs and screenshots are not supported. Open the editor's API reference to see the supported commands. Unsupported commands produce an error.
Which frameworks and languages are supported?+
Use Playwright with TypeScript, Cypress with JavaScript, or Selenium WebDriver with JavaScript. Finding elements, waiting and checking results are also useful in other languages. The test code looks different in each language.
Do I need an account?+
No account is needed to run or verify tests, or use the free test review. Sign in to share progress across devices. Mock interviews and publishing or revoking report links require sign-in. Purchases and paid lectures also require an account.
Is my code sent to a server?+
Practice runs, grading and the free test review process your code in your browser. Saving account progress does not upload your draft code. Publishing a report uploads and stores the code in that report. Anyone with the link can read it until you revoke access. Submitting work during a mock interview sends code and results to the server. The AI interviewer receives that code for feedback. The interview conversation is stored.
Who is TestAcademy for?+
Manual testers can start writing automated tests. Students and working engineers can practise browser testing or try another framework. You can also prepare for QA and test automation interviews.
What does the Run tests button check?+
The Run tests button checks your tests against the working practice app. It shows which tests pass or fail, plus code review findings. A pass does not prove your test catches a bug added on purpose. Use Verify for that check. Running tests alone does not mark a problem solved. Free-play practice has no graded completion step.
What does Verify check?+
Verify checks whether your test catches the bugs required by the problem. First, fix any code review issues that block grading. Your tests must then pass on the working app. Next, they run against app copies with something broken on purpose. Each copy is checked separately. Each broken copy must cause a test failure. An error that stops the code running does not count as catching a bug. The result names the required bugs caught and missed. It does not check every possible bug. Fix and fill exercises use the same check. Their buttons are called Check fix or Check.
When is a graded problem marked solved?+
Write, fix and fill problems require verification to catch every required bug. Debug and refactor exercises use Grade instead. Debug exercises repeat tests and change their order. They also reject fixed sleeps. A fixed sleep pauses for a set time instead of waiting for a result. Refactor exercises require verification to pass with no code review findings. A successful grade saves the problem as solved. Changing a test title does not complete a problem.
Where are my code and progress saved?+
Your draft code and progress are saved in this browser when browser storage is available. Clearing browser storage removes that saved data. If storage is blocked, your work may be lost when you leave or reload. Signing in shares solved problems, completed lectures and interview-practice scores across devices. Draft code stays in the browser where you wrote it. Sign in there first to upload its progress. Use the same account on another device to load that progress. Sharing progress needs an internet connection and an available service. If it fails, saved local progress remains in your browser.
How can I report a bug or suggest a topic?+
Email contact@testacademy.dev. Say which page you used and what happened. For a bug, include the steps needed to see it. You can also suggest a lesson topic.