Amikoo FAQ

Amikoo is an AI-based, end-to-end testing platform. It generates and maintains Playwright test suites directly in your repo: creating tests, opening pull requests, and repairing failures automatically.

Playwright. Coming from Selenium? Amikoo also helps migrate your existing suite to Playwright.

Yes, for web apps, including modern JS-based apps. It works with standard username and password logins. It can't complete 2FA logins automatically, though our team can help set up access for exploration only, this doesn't affect your automated tests. It's built for web apps only, not native mobile apps.

Sign up at qa.amikoo.ai. Integrate GitHub or Azure DevOps, add your app's name and URL, and add context files about your app. All optional but recommended. Once that's done, start asking Amikoo questions right away.

No. Amikoo generates tests from scratch by analyzing your application, or finds coverage gaps if you already have a suite.

Ask through AmikooChat. Request specific scenarios or ask for suggestions on what to test next. Amikoo avoids duplicating existing coverage.

Yes. Amikoo generates tests and opens a pull request in your repository, rather than keeping them in a separate system.

A worker is a task Amikoo runs each time it's triggered: on a schedule you set, or on an event like every pull request.

Basically anything Amikoo can do: create tests, repair failing tests, create issues, send reports, and more.

No hard limit on running workers in parallel. Every worker action uses credits, so your credit balance determines how much you can run.

Amikoo generates standard Playwright tests, so you can run them however works for your team: locally or in your own CI. Run them from Amikoo's cloud and they execute headless on Chromium.

Add the Amikoo reporter to your Playwright project and connect it with your Amikoo key. From then on, every run, local or CI, sends results automatically to your Amikoo dashboard.

From the Amikoo dashboard, explore executions and view feedback for each run. The same content is available on the tests page.

A classifier decides when a failure should trigger automatic self-repair. Any self-repair changes arrive as a pull request too, just like new tests.

Yes. Every change, new tests or self-repairs, arrives as a pull request. There's no separate approval step inside Amikoo: the PR is the control point, so you always have the final say.

Yes. The trial includes a 50,000 credit limit, roughly enough for 40 questions or interactions with Amikoo.

Contact our team directly. This isn't self-service from account settings today.

In Account Settings inside the platform, where you can manage your configuration, including API keys.

Yes, through the GitHub integration, the AmikooAI app, with read and write access. You choose from GitHub whether to grant access to specific repos or your whole org, and you can revoke access anytime from GitHub or Amikoo.

Hosted in the US on secure cloud infrastructure. Retention ranges from 7 to 365 days depending on data type: backend and chat logs for 365 days, files for 30 days or less.

Amikoo is currently pursuing SOC 2 certification. Not yet certified.

Yes. Point Amikoo at any environment you need, including staging. If your app sits behind a firewall or VPN, that can affect exploration and test execution. Our team can help with setup.

GitHub and Azure DevOps to connect your repo, open pull requests, and manage test runs. Bitbucket and GitLab are coming soon. Slack for reports and notifications. Jira to read and create issues, use them as context, and comment back with updates.

Use the in-app chat, or email karla.borrallo@amikoo.ai. The Contact Us link and Book a Demo are also available for commercial questions.