Testera IO

Our CI already runs through GitHub/GitLab so I’d rather not add another tool that forces the team to change how we work. Testera fitting into the existing setup makes more sense, especially if we can use the same pipeline while getting the test management and failure triage separately. How much setup is actually needed to connect an existing CI pipeline to Testera?

We’ve used TestRail for our test cases, so I was checking out how Testera handles that side of things. Being able to connect the two first instead of moving everything on day one is pretty good. It gives the team some time to see how Testera fits before making a full switch. BTW, love that you’re not forcing teams into a hard cutover.

The webhook part is pretty interesting for anyone who has their own automation running around CI. I’d want the event to carry enough detail to know what happened which suite was affected and what the result was without making another request to Testera. That would make it much easier to plug into our own scripts and tools.

I wasn't expecting the free plan to include 3 seats and 500 test cases. That's enough room to actually try Testera with a small project instead of just playing around with a limited demo. The 25 AI credits every month are a great extra too, especially with the AI Companion and MCP access included. For a $0 plan, there's a lot here to get started with. Hope the launch brings good early users.

A REST API is important when we already have scripts doing part of our testing. Being able to trigger runs or pull results from code means we don't have to keep jumping into another dashboard. That's the kind of thing that makes a QA tool easier to fit into an existing setup. Are the API keys scoped per project, or is it one key for the whole workspace? :)

Waiting for a full test run to finish just to see where things went wrong can be frustrating. Live progress in Testera would make it easier to see what is running and spot problems as they come up. I’d also want the results to show up while the run is still going, so I can start looking into an issue without waiting for everything to finish.

The Jira, Slack and Sentry connections would be handy once you're dealing with a constant stream of test events. I'd probably want to control which events get sent to each one. For example an actual failure could open a Jira issue, while routine test updates could stay in Testera or go to Slack. That would save us from getting a notification for every little test event.

I checked out your launch on Product Hunt and while reading the description I saw you have 20 years of engineering experience. Pretty cool. You’ve probably seen the same testing problems come up again and again over the years. The part about test maintenance taking up so much time caught my attention. It’s easy for a test suite to grow and become hard to keep up with. That got me thinking about the story behind Testera. Was there a specific problem that made you decide it was time to build something for it?

Security and access controls matter more once a QA tool is used by a whole team. Things like roles, audit logs and 2FA give admins more control over who can see or change things. I also like the idea of the offline-friendly PWA because not every dev environment has a perfect connection all the time. Having both the access controls and a way to keep working when the connection drops makes the product feel more practical for day to day use. A question for you: If the connection drops during a run does the PWA keep the work going...?

I’ve used a few test management tools where test cases, runs and plans start getting messy once a project grows. How does Testera keep those things organized when the same test case is used across different runs or projects?

@Selina Yes automation/agents working in the background , you can have as many as you need and when they get triggered or executed on demand there is a log/summary of what exactly was done.

If I add a few AI or prompt tasks to the queue, can Testera work through them in the background and mark each one complete when it's done? And can I see what the agent did for each task afterward?

Hey Victor! Yes its all AI driven so u can ask it to create projects , plans, tests, automation etc… for u!

If we connect Testera to Claude or Cursor through MCP, can the assistant create and update test cases directly from the conversation? And does Testera keep those changes linked to the right project and test suite?

Just signed up.... I like it a lot. So many features!!!!

The small QA jobs are the ones that keep getting pushed back when the team is busy. Having scheduled recipes for things like health checks and flaky test reports could take some of that work off our plate. Instead of someone remembering to run these checks every week, Testera can handle them on a schedule and give the team the results when they're ready. Hope the launch goes really well for you guys.

Klara, you connect your MCP to Jira, GitHub, and other tools to give the AI the context it needs. When a test fails, it can determine whether the failure is caused by a real product bug or an issue with the test itself. If it’s a test issue, the AI can open a self-healing pull request with the proposed fix. If it’s a product bug, it can create a detailed Jira ticket and identify the GitHub pull request that likely introduced the regression. GitHub and Jira are just examples—you can connect the tools your team already uses, including GitLab, Bitbucket, and others.

Monday mornings can be rough when I open CI and see a pile of failed tests. I end up digging through logs just to figure out which failure actually matters. Testera's failure triage could save me a lot of that time by grouping similar failures and helping separate flaky tests from real bugs. How does Testera decide which failed tests belong to the same issue?

Yes agents explains everything and generates full report that is also stored un Testera artifacts. It also has test gap discovery and many more automation recipes that you can use .

Draft-PR heals with a human always approving the merge is the right default for auto-fixing CI. Does the agent explain its diagnosis in the PR description?