Everything people ask about Sekee.

Test case management is keeping your test cases, the runs you execute them in, and the results those runs produce in one system instead of scattered across spreadsheets. It gives every test a single owner, a history and a current state, so "does this still pass?" has an answer you can look up rather than a person you have to ask.

It stores your test cases, organises them into a structure your team can navigate, schedules and records runs of them, and reports what the results mean. Sekee adds the parts testers do between those steps: timeboxed bug hunts before a release, exploratory sessions against a charter, and automation results reported in from CI alongside the manual ones.

• See every feature

For one tester and a handful of features, yes, and you should. A spreadsheet stops working when more than one person edits it, when you need the history of a test rather than its current row, when results have to come back from CI automatically, or when someone asks what changed since last release. Those are the four things it cannot be made to do, and they all arrive at once.

Jira tracks work; a test management tool tracks coverage. They answer different questions — Jira tells you what the team is doing this sprint, Sekee tells you which parts of the product are actually verified and when they were last checked. Sekee pushes issues straight into Jira and links them back to the test case or bug hunt that found them, so you are not choosing between the two.

Both, in the same place. Write and run manual test cases, and report automated runs in from CI so the two sit side by side against the same product. Most teams have both and keep them in separate tools, which is why nobody can answer what overall coverage looks like without building the picture by hand.

Software teams that test — QA engineers, testers, developers who own their own quality, and the people who need to see the result. It suits a team of five upwards, and it is built for teams that want to write a test case in under a minute rather than configure a process first.

Same core job — test cases, runs and reporting — with far less to configure. Sekee adds bug hunts, exploratory sessions and a kept history of every automation run, plus short-term viewer access, so you are not buying a full seat for someone who logs in twice a month. Zephyr and Xray live inside Jira; Sekee is a tool of its own that integrates with Jira.

• Sekee vs TestRail
• Sekee vs Zephyr
• Sekee vs Xray

Yes. Sekee reads CSV, TSV, Excel workbooks, JSON, and TestRail or TestLink XML — which covers the export every major tool offers, since TestRail, Zephyr, Xray, qTest, Qase and Testmo all write CSV or Excel. Drop the file in and Sekee works out the column names and the step layout on its own, showing you every guess as a control you can change before anything is written.

No. Most teams start with one project and one suite, and nothing stops you running Sekee alongside whatever you use today. The importer is there for when you want it, not a wizard you have to sit through first.

Minutes to a first test case. Create an organization, create a project, write a case with steps and expected results — there is no test plan hierarchy to design first and no workflow to configure before the tool will accept anything. Connecting Jira or a CI pipeline is a separate step you can take whenever you are ready.

There is a live demo on this site that runs the real interface in your browser with no account and no email address. It is the product, not a video, so you can write a test case in it and see how the app actually behaves before you decide anything.

• Try the live demo

Any runner that produces JUnit XML — Playwright, Cypress, Jest, pytest, Vitest, JUnit itself, whatever you already have. Post the report with an API token at the end of your pipeline and it lands as an automation run, with every test in it kept as a result you can look up later.

Every framework that can write a JUnit XML report, which in practice is all of the common ones: Playwright, Cypress, Jest, Vitest, pytest, JUnit, TestNG, PHPUnit, RSpec and Go test with a reporter. Sekee reads the report rather than integrating with the framework, so a runner nobody has heard of works exactly as well as a popular one.

Yes. Because every run is kept rather than overwritten, Sekee can see a test that passes and fails against the same code and flag it as unstable. You get pass, fail and flake history per test, so a test that has failed intermittently for three weeks is visible as that rather than as today's red tick.

• See every feature

Yes. Link a test in an automation run to the test case it covers, and that case then shows its automated history alongside its manual one. It is how you stop maintaining two parallel pictures of the same coverage.

A bug hunt — often called a bug bash — is a timeboxed group test before a release, where several people explore the same build at once to find what structured testing missed. In Sekee you create the hunt, load it with test cases, assign them across testers and developers, and collect bugs and comments as people work.

A bug hunt is a group event with a fixed window and assigned coverage; an exploratory session is one tester working unscripted against a charter. Every bug hunt uses exploratory testing, but most exploratory testing is not a bug hunt. Sekee has both, because they answer different questions — breadth before a release, and depth whenever a tester wants it.

You start a session against a charter — what you intend to explore and why — and Sekee keeps a timed record while you capture notes and issues as you go. At the end you have evidence of what was covered and what it cost, which is the thing exploratory testing is usually criticised for not producing.

That is what viewer access is for. Invite a developer, a designer or a product manager as a read-only guest for three days rather than buying them a full seat, and they can follow the hunt and comment on what they see. Every plan includes three free viewer invitations a week for each five seats.

Starter is $49.95 a month for five seats and $9.99 for each seat after that. Standard is $64.95 for five seats and $12.99 per extra seat. Business is $79.95 for five seats and $15.99 per extra seat. Every plan is month to month with no contract and no minimum term, and the pricing page has a calculator that quotes your exact team size.

• See pricing

There is no free plan, but every plan starts with a free trial and no card is needed to begin it. The trial is 14 days; organizations that sign up by 30 November 2026 get 60 days instead, as a launch offer. You can switch plans or change the team size while it runs. When it ends, everything you created stays readable, but nothing new can be added until the organization is on a paid plan. Paid plans start at $9.99 a seat a month on Starter, with a five-seat minimum. The live demo on this site needs no account at all.

• Compare the plans

Because the plan price is simply five seats at that plan's seat rate — $9.99 each on Starter, so $49.95. A seat beyond the fifth costs exactly what a seat inside the first five does, so there is no bulk step and nothing to negotiate. Below five people, Sekee is not the tool to reach for.

A seat is a full login: it can create and edit test cases, run bug hunts and exploratory sessions, and see everything in the project. A viewer is a read-only guest invited for three days, for someone who needs to look rather than work. Every plan gives three free viewer invitations a week for each five seats, and the allowance resets weekly. If someone needs permanent read-only access, a viewer seat costs 40% of a full seat.

Yes, at any time. The organization owner changes the seat count from the billing screen and the monthly price moves with it. Seats are not tied to named people either — when someone leaves, their seat goes back to the team.

Yes, in either direction and at any time. The organization owner switches between Starter, Standard and Business from the billing screen, and everything already created comes with you — no migration, no re-import, no re-configuring. Before a downgrade, Sekee checks the plan you are moving to against what you actually have and warns you if something would no longer fit, such as more projects or dashboards than the smaller plan allows.

• Compare the plans

The organization owner cancels from the billing screen, and there is no contract or notice period to work through. Cancelling does not delete anything: every test case, run, session and attachment you already have stays in place and stays readable. What stops is creating new ones — the organization keeps its full history and waits for you, so coming back is choosing a plan again rather than starting over.

Nothing immediate. A failed payment opens a grace period of about a week before anything changes, so a card that expired mid-sprint does not lock your team out on the day it happens. If it is still unresolved after that, the organization falls back to the same read-everything state as a cancellation — nothing is deleted.

Only the organization owner can change the plan, and owners and admins are the only roles that can see the billing screen at all. Members and viewers cannot see what you pay. It is enforced on the server rather than by hiding a button.

Yes, at any time and without asking anyone. Export test cases as CSV, an Excel workbook, JSON, TestRail XML, TestLink XML or PDF — the XML formats keep your folder tree, and the first three are read by every other test management tool. There is no export you have to request and no format designed to be hard to leave with.

It stays in your organisation, isolated from every other tenant, and it is never shared with or sold to anyone. Deleting an organization is deliberate and reversible for a week: the owner has to confirm it, everyone in the team is emailed, and the erasure is scheduled rather than immediate so a mistake can be called off.

Test artifacts — bug hunt screenshots and automation run reports — are kept for 30 days on Starter and Standard and 90 days on Business. Your test cases, their steps and their attachments are never removed by retention, whatever plan you are on and however long you have been on it.

Two-factor authentication is on every plan, and it is deliberately not a paid feature — charging for a security control is the pattern vendors have been asked to stop. Sign-in with an existing Google account is available on every plan too. Neither switches off if a subscription lapses.

Yes. Owner, admin, editor and member roles decide what each person can do, and viewers are read-only by definition. Standard and Business also keep an audit log of who changed what and when, so a change can be traced back to the person who made it.

Yes, on every plan. Sekee runs an MCP server, so an AI assistant that speaks the Model Context Protocol can read and write your test cases directly — drafting cases from a requirement, or summarising what a suite covers. Anything an assistant does is recorded as having been done by an assistant, on every plan, so the audit trail never quietly attributes it to a person.