What Sekee is
Sekee is a test management platform for teams whose testing is part written down and part run by machines. It holds the test library, the runs people do by hand, the runs CI does overnight, the bugs both of them find, and the thread that ties all of it back to what somebody asked for in the first place.
It is built around one idea: coverage is derived, never declared. Nobody marks a requirement "covered". Sekee works it out from the last verdict on every test case linked to it, the bugs still open against those cases, and the last result of every automated test standing in for them. A requirement stops being covered the moment the evidence stops saying so.
What is in it
| Area | What it is for |
|---|---|
| Dashboard | Your own summary: what's yours, what needs a look, right after you sign in |
| Test library | Test cases in folders, with steps, attachments, shared steps and custom fields |
| Bug hunts | A scheduled event where named people execute chosen test cases and record verdicts |
| Sessions | Timed exploratory testing against a charter, with notes and bugs logged as you go |
| Bugs | Everything the hunts and sessions found, across every one of them, in one list that outlives them |
| Requirements | Jira issues or hand-written statements, with coverage derived from the runs |
| Automation | JUnit/XML reports from CI, parsed into runs, tests and per-test history |
| Error tracking | One row per distinct failure across runs, with an occurrence count |
| Visual testing | Screenshots from CI compared against approved baselines, with a page to approve or reject what changed |
| Analytics | Boards of widgets over any of the above, per project or across the organization |
:::note Recently changed Analytics used to be called Dashboards, with a sidebar item that said Dashboard. It was renamed because the thing you build there is a board, not a dashboard. The sidebar now has a Dashboard item again, above Analytics — but it is a new, different screen: your own personal summary, not the boards page. See Dashboard. If your instance's sidebar has a Dashboard item that opens the boards page instead of a personal summary, it predates this second change. :::
Two ways in besides the browser
sekee-clipushes test reports from CI into Sekee. One command for a simple run, orinit/thread/completewhen parallel shards finish at different times.- The AI connector is a Model Context Protocol endpoint you point your own assistant at. It reads and writes through the same permissions you have, so an assistant cannot do anything you could not do yourself.
How this manual is arranged
Read Quickstart if you want something on the screen in ten minutes, and Core concepts if you want to understand the shape of the thing before you commit to it. Everything after that is organised by the job you are doing, and the Reference section at the bottom is for looking up rather than reading.
:::note About versions This manual describes the current release. Where behaviour changed recently and you may still be running the older version, the page says so explicitly. :::