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. It is two steps: your account — a work email and a password — and then your organization, the tenant that owns everything else. You become its owner.

Every URL in the app is scoped to the organization: /{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.

:::note Recently changed Signing up used to ask for the organization name first and the account second. The two steps swapped, so the form now opens on Create your account. Nothing about what gets created changed — only the order you are asked in. :::

Agreeing to the terms​

The account step has a checkbox you must tick to continue:

I agree to the Terms of Service, the Data Processing Agreement and the Acceptable Use Policy, on my own behalf and for the organization I am creating, and I have read the Privacy Policy.

Each document name links to its page. Under the checkbox is a reminder: don't store sensitive personal data, confidential business information such as trade secrets or unreleased financials, passwords, API keys, or production customer data in Sekee. If a document changes while the form is open, Sekee sends you back to this step to read it and tick the box again.

People you invite later accept the Terms of Service, the Acceptable Use Policy and the Privacy Policy when they join. They do not sign the Data Processing Agreement. The owner signs that for the organization. See Legal documents and your data.

Confirming your email​

Right after signing up you get a Confirm your email email. Open the link and press Confirm my email. The page does not confirm the address just by opening. The welcome email arrives after you confirm.

You can use Sekee straight away, but until you confirm you cannot:

  • invite members,
  • upload files (attachments, screenshots, your profile photo),
  • create API tokens for CI,
  • create AI connectors.

A banner across the top says so, and it has a Resend the email link. You can resend once every two minutes.

  • After 3 days without confirming, all you can do is sign in and confirm. A full-screen prompt asks you to confirm. Nothing you created is lost.
  • After 14 days, an organization whose owner never confirmed is deleted automatically, as long as the owner is its only member.
  • The link works once and lasts 7 days. If it has expired, sign in and use Resend the email.

Invited members don't need to confirm anything. Accepting the emailed invitation already proves the address.

:::note Recently changed Email confirmation is new. Signing up used to send the welcome email straight away, with no confirmation and no limits. Accounts created before the change count as confirmed and are unaffected. :::

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 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 → Create.
  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​