Click through your app
Tenaqa opens your app in its own browser and turns every click, entry and check into a readable step, with the strongest locator it can find.
Pilot program now open
Record your app.
Own the Playwright code.
Tenaqa is a desktop studio for QA engineers. Click through your app the way you test it, and get clean, readable Playwright tests in your own repository, with backup locators that keep them holding when the UI changes.
Playwright · TypeScript · macOS and Windows
- 1Open the login pagepage.goto('/')
- 2Sign in as customergetByTestId('login-submit')
- 3Add “Pliers” to the cartgetByRole('button', { name: 'Add to cart' })
- ✓Check the cart shows “1”toHaveText('1')
test('Happy path', async ({ page }) => { await page.goto('/'); await login.signIn(data.customer); await catalog.addToCart('Pliers'); // backups kept per step await expect(cart.badge()) .toHaveText('1'); });
How it works
From a click-through to a test suite in minutes
No framework to set up and no scripts to write by hand. Tenaqa builds the project, the page objects and the tests as you go.
Tidy it up in plain language
Rename steps, add checks, swap typed values for test data and keep passwords in .env. Re-record from any step if the flow changed.
Run it, then take the code
Run scenarios, suites or the whole project with clear pass and fail reasons. The output is a standard Playwright project you can commit and run in CI.
Features
Built the way QA teams already work
Features, suites and scenarios. Tests that read like test cases. Code that a developer would happily review.
Code you own, no lock-in
Plain Playwright and TypeScript with page objects and shared helpers. No runtime, no proprietary format, nothing to keep paying for to run your tests.
Features, suites and scenarios
Group the happy path and its edge cases in one suite: “Add employee”, “Existing employee is rejected”, “Invalid data”. Run one, a suite, or everything.
Re-record from any step
The app changed after step 5? Tenaqa replays steps 1–4, you record the rest, and you compare before you save. The previous version is one click away.
Secrets stay secret
Passwords live in each project’s .env, are masked in every report and never end up in the generated code.
Clear results
Every step shows passed or failed with a screenshot and the reason, in words a tester can act on, not a stack trace to decode.
Runs on your machine
A desktop app for macOS and Windows. Your app, your test data and your code stay on your computer and in your repository.
Mend
Tests that hold when the UI moves
Most recorded tests break the first time a developer renames a class. Tenaqa keeps more than one way to find every element, so a test can hold on and tell you what changed.
- Every step stores a ranked set of locators: test id, role, label, text, then CSS.
- A backup is kept only if it points at exactly the same element.
- When the main locator fails and a backup holds, the run says so, so you fix it on your terms.
Main
#btn-add-to-cart-2no matchBackup 1
getByRole('button', { name: 'Add to cart' })heldBackup 2
getByText('Add to cart')not neededStep 3 passed on a backup locator. Update the main one?
Pilot program
Help shape Tenaqa from day one
We’re working with a small group of QA teams to build the first release around real projects.
- Early access to the desktop app for your team
- Direct line to the founder, and your requests on the roadmap
- Founding-team pricing, kept as long as you stay
- Help setting up your first suites on your own app
Request a pilot spot
Tell us a little about your team, the app you test and how you test it today. We reply to every request.
Email hello@tenaqa.comBest fit: teams testing a web app with a dedicated test environment.
FAQ
Questions QA teams ask first
Do I need to know how to code?
No. You record, review and run tests in plain language. The code is there when you or your developers want it, and it’s written to be read.
What do I get at the end?
A standard Playwright project in TypeScript: specs, page objects, helpers and a config. Commit it to your repository and run it in CI like any other Playwright suite.
Where do my app data and passwords go?
Tenaqa runs on your computer. Recordings and code stay in your project folder, and passwords stay in the project’s .env file, masked in every report.
Which apps and browsers does it support?
Web apps, recorded and run in Chromium during the pilot. Logins, forms, single iframes and file uploads are covered. Tell us what your app needs; that’s what the pilot is for.
What about Cypress, Selenium or mobile?
Playwright comes first. More frameworks are planned, each as its own studio in the same app.