Skip to main content

Quickstart

This walks from an empty account to a test case that has been run, a bug that was found running it, and a requirement that knows about both. It takes about ten minutes and uses nothing but the browser.

1. Create an organization​

Sign up at your Sekee instance. The first thing you create is an organization — the tenant that owns everything else. You become its owner.

Every URL in the app is scoped to it: /{your-org}/test-cases, /{your-org}/bug-hunts, and so on. If you belong to more than one organization, the switcher at the top of the sidebar moves between them.

2. Create a project​

A project is the unit of work inside an organization — usually one product, one application, or one team's area. Test cases, bug hunts, sessions, requirements and automation runs all belong to exactly one.

Create one from the project picker at the top of the sidebar. Sekee gives each project a per-organization sequential projectId, which is the number CI uses when it uploads reports.

3. Add a folder and a test case​

Go to Test Cases. The left pane is a folder tree; the right is the library.

  1. Create a folder — Checkout, say.
  2. Create new inside it.
  3. Give the case a name, a description, and any pre-requisites.
  4. Add steps: each has an action, an expected result, and optional data and screenshots.

Save. The case starts in the In progress state; move it to Active when it is ready to be run.

4. Run it in a bug hunt​

A bug hunt is an event: a name, a window, some people, and a set of test cases to get through.

  1. Go to Bug Hunts → New bug hunt.
  2. Name it, pick the project, set the dates, add yourself as a member.
  3. Add the test case you just wrote.
  4. Open the hunt and click into the case.

You now have an execution screen: the steps on the left, a verdict per step, and a verdict for the case. Mark a step failed and record what happened — that is a bug, and it belongs to the hunt, the case and the project all at once.

5. Tie it to a requirement​

Go to Requirements → Link requirement. If your Jira is connected you can search it and pick the issue; otherwise write the requirement by hand.

Link the test case to it. The requirement's coverage is now derived from the verdict you just recorded — and from the open bug, which will hold it down until somebody closes it.

6. Send a run from CI​

Install the CLI and push a report:

npm install -g @sekee/sekee-cli
export SEKEE_API_TOKEN="…"    # Administration → API Tokens

sekee-cli upload-reports \
  --url https://api.sekee.io \
  --name "Nightly regression" \
  --projectID 1 \
  --source "GitHub Actions" \
  --reports "./reports"

The run appears under Automation. Open it, find a test, and link it to your test case — from then on that case's coverage follows CI as well as people.

Where to go next​