You point at the ticket. It writes the cases, runs them in the browser and fixes itself when the screen changes.
Runs in your browser. Nothing to install.
from what you already have: a ticket, a document, a single paragraph.
in a real browser, in the cloud, with video and evidence of every step.
when a selector breaks, it rewrites itself and keeps going.
A test management tool records what happened.
Qymar makes it happen.
The site changed. A button moved. The test no longer wrecks your day.
When an element changes, it rewrites the locator on its own, runs again and keeps going, and records exactly what changed, for you to review.
Only something that's there when it breaks can fix it.
Video and screenshots of every step, opening in the browser with nothing to install. You send your manager the link and you're done.
No spec to write, no spreadsheet to fill in, nothing to prep.
a ticket, a document, or just a pasted paragraph.
it pulls what's scattered around: the description, the discussion comments, the acceptance criteria on the parent item, the attachment.
the scenarios, plus scripts that actually run.
Every rung below works on its own. You're never blocked because a doc is missing.
Every rule in the requirement is traced to the scenario that tests it. Whatever's left out shows up, with a button to fix it.
At launch: paste the requirement or upload the document, ready scenarios and scripts, cloud execution with video, self-repair, a schedule that warns you when something breaks, and a connection to the tool where your requirement already lives.
After launch (and you, as a pioneer, help set the order): the 4-question interview, screen recording, the coverage matrix, and testing installed desktop software.
No machine left on, no scheduled task on anyone's computer, nobody on call. You set the hour and go to sleep.
Something broke overnight? It tries to rewrite the selector and carry on. If it can't, the email is already waiting when you wake up, with video of the step that failed.
No feature depends on an integration: pasting the text works just the same. Connecting is what stops the case from being copied by hand.
| Starting from | Test cases | Runs | Bugs |
|---|---|---|---|
| I don't use any of these tools | at launch | at launch | at launch |
| Azure DevOps / TFS | at launch | at launch | at launch |
| Jira | later | later | later |
The capabilities are composable: keep everything here and send only the bugs to your tracker, for example. And when the system you test only exists inside your company network, an agent with no interface runs in there and sends the result back, without opening anything up to the outside.
A hosted product has to answer this before being asked, not after the first scare.
Every run gets its own virtual machine, with its own operating system, created for it and destroyed at the end. Nothing is reused between runs, let alone between customers.
It isn't a check somebody has to remember to make: it's the only way the product can reach a file at all. One customer cannot ask for another one's path.
A test video is your screen, and sometimes it holds data belonging to people who never heard of us. It's deleted on your plan's schedule, and the sharing link expires with it.
Never a real person's account, never an administrator's. That protects you from us, and protects both of us from an accident at 3am.
Credentials never reach a log, an error message, a URL, or what is sent to the model. And no data of yours trains any model.
| Capability | Qymar | Test management | Open frameworks |
|---|---|---|---|
| Actually runs the test, end to end | yes | no | yes |
| Fixes the selector on its own, the moment it breaks | yes | no | no |
| Runs at the hour you set, with no machine left on | yes | no | with your own CI |
| Nothing to install, nothing to maintain | yes | yes | no |
| Starts from a thin ticket or no spec | yes | partial | no |
| Video and evidence of every step, with no setup | yes | manual | with your own CI |
When all you need is to organize cases and reports for a large team, a test management tool can be the right call. When you need to run the test, it's here.
Limited seats: the first 15 people on the list get 30 days free at launch. Every new account starts with 7 days. You're among the first to run it when it opens, and you help shape v1.