Questions, answered honestly

It scans an existing Selenium or Cypress test suite, generates a migration readiness report, and converts the tests to Playwright. The conversion is AI-assisted: a deterministic rule engine handles the common cases identically every time, and a Claude-based fallback handles the long tail with full project context.

Sign in, then either upload a folder of test files or connect a public GitHub repository from the dashboard. The scanner produces a report in a few minutes; the report page has a 'Convert All' button that generates the Playwright project.

No. TuscanoLabs runs entirely in the browser plus our backend — there is no CLI, no GitHub App to install, and no agent to run inside your repo. For private repositories you connect your GitHub account via OAuth and we read the repo on demand.

Analysis usually finishes in under a minute for small to medium projects. The full Convert All flow takes longer because it processes each file individually and runs validation — expect a few minutes for a typical suite, more for very large repos.

Selenium (JavaScript, TypeScript, Java, Python) and Cypress (JavaScript, TypeScript, Cucumber/BDD) are fully supported today. WebdriverIO, TestCafe, and Puppeteer are on our roadmap — contact support@tuscanolabs.com if you need them.

On the source side: Java, Python, JavaScript, and TypeScript. On the target (Playwright) side: TypeScript, JavaScript, and Python. C# support is on our roadmap. You pick the target language at conversion time.

JUnit 4, JUnit 5, TestNG, pytest, unittest, NUnit, xUnit, MSTest, Mocha, Jest, and Vitest. Detection runs against your config files, imports, and annotation patterns — not just file names — so it works on non-standard layouts.

Yes. The scanner detects POM, Cucumber/BDD, and API-test architectures. POM repos generate Playwright POM classes with fixtures, BDD repos generate playwright-bdd feature and step files, and mixed codebases get a per-area recommendation rather than a forced one-size structure.

Not currently in scope. TuscanoLabs targets web test migration. Appium and electron-specific Selenium patterns are not on the supported list today.

No. The first layer is a deterministic rule engine — the same input always produces the same output. The Layer 2 AI fallback is only invoked for code the rules don't cover, and even then the AI gets the file's helpers, page objects, and project context as part of the prompt rather than a snippet in isolation.

It depends on the codebase. Standard Cypress and Selenium suites with conventional architecture typically auto-convert most files; suites with heavy custom commands, deep helper chains, or non-standard fixtures need more review. Your scan report shows a real readiness score for your specific code, not a generic claim.

They are flagged in the report with a specific reason — for example, 'unrecognised custom command', 'unsupported assertion library', 'helper file missing'. They are not silently dropped or replaced with placeholders. You can hand-edit them in the conversion preview or regenerate them with the AI after fixing the upstream issue.

Yes. After Convert All runs, the conversion preview page shows a side-by-side diff for every file. You can edit any file inline, regenerate a single file, or report a specific issue. The download is a ready-to-run Playwright project ZIP.

No. We aim for runnable-on-day-one and most files achieve that, but selectors against a real application sometimes need adjustment, environment-specific config has to be set, and any test that depended on a custom plugin will need that plugin replaced. Treat the output as a strong starting point, not a final commit.

New accounts get 3 free scans with no credit card required. Beyond that, pricing depends on conversion volume — contact support@tuscanolabs.com for details specific to your team.

Not as a separate plan. The 3 free scans on a new account are the same regardless of whether the repo is open or closed source. If you're maintaining a high-impact open source project and want to discuss something more, get in touch.

Yes — there are practical limits on the number of test files we will process per scan to keep response times reasonable. Very large monorepos may need to be scoped to a sub-directory. The scanner reports any files it skipped due to size or type filters.

Uploaded source files are stored alongside your report so that conversion preview, regeneration, and ZIP download work after the initial scan. They are automatically purged 30 days after the scan, or immediately when you delete the report from your dashboard.

No. AI conversion uses Anthropic's Claude API under their commercial terms, which contractually prohibit using API inputs or outputs for model training. We do not feed your source code into any training pipeline of our own either.

Tokens are encrypted at rest using AES-GCM with a key managed outside the database. Connecting GitHub stores only the scoped OAuth token; disconnecting GitHub immediately deletes it. Read paths only use the token to fetch the specific repository you authorise.

No. Every customer-data table has row-level security policies that scope rows to the account that created them. Other accounts cannot read or query your data, even with a known report ID. Service-role access is restricted to backend code that already verifies ownership.

Not yet — and we won't claim to be. The Security page lists the controls we actually implement today (TLS, encryption at rest, RLS, rate limiting, sanitised logs, dependency monitoring, code review). If your procurement process requires a specific certification, get in touch and we can talk about what we can share.

You can delete individual reports from the dashboard at any time, which also removes the stored source files for that scan. Account deletion is available on request via support@tuscanolabs.com — we will respond within 30 days, in line with the GDPR rights described in our Privacy Policy.

Yes. Reports can be exported as PDF for stakeholder review, and converted projects download as a Playwright project ZIP that's ready to run.

Two common causes: (1) the report was generated by an upload flow without source files attached, or (2) a Convert All run has not been triggered yet. Open the report and click Convert All to generate the converted files.

GitHub OAuth tokens expire over time. Reconnect GitHub from the dashboard — the connection screen will prompt you to re-authorise — and retry the conversion.

Open the file in the conversion preview, click 'Report issue' in the bottom action bar, and pick the category that fits. The feedback is logged against that specific file and informs which patterns we improve next. You can also regenerate that file with the AI to try a different output.

Email support@tuscanolabs.com. We read every message.