Skip to content
certyn logoCertyn
Start Free
RecipesDoc

Turn a Jira Story, a Spec or a PRD into Test Cases, Then Run Them

Certyn reads a story or a document, writes test cases with steps and expected results, tags them, and runs them on your environment.

For QA leads who get requirements as Jira stories or documents and need test cases fast.

Your setup

  • A Jira story with acceptance criteria, or a spec or PRD as a PDF or Markdown file.
  • The feature is on staging, with a test account.
  • You want test cases in Certyn, grouped by a tag, and a first run.

Say this to Certyn

Read SHOP-214 and write test cases for its acceptance criteria, tagged checkout and smoke. Then run them on staging.

Or attach the PRD and say: Write test cases from this PRD, tagged billing.

What Certyn does

  1. Reads the requirement. A Jira, Linear or GitHub issue it reads through your connection (tracker.issue.get); if Jira is not connected, it opens the connect form. A document you attach in the web chat: PDF or a text file (Markdown, TXT, CSV, JSON, YAML), up to 10 MB each.
  2. Searches the test cases you already have (app.find), so it updates a matching case instead of adding a duplicate.
  3. Writes the cases: one behaviour each, with preconditions, numbered steps, expected results and test data. Secrets appear only by variable name, like LOGIN_PASSWORD.
  4. Saves them with your tags (app.testcase.create).
  5. Runs them (app.run.create type test_case, up to 50 at once), or creates a suite for the tag (app.process.create type certyn) and runs it. It asks before it starts a run.
  6. Reports each result. A failure is either a product bug (filed as an issue with evidence) or a wrong step in the case, which Certyn fixes (app.testcase.update).

What you get

  • Test cases for the story's acceptance criteria, tagged as you asked.
  • A first run with a result per case.
  • With the smoke tag, the cases join the Smoke Suite, which runs after each deploy. Without tags, they get regression and run nightly.

Limits

  • Cases written from a document are not yet checked against the app. The first run shows which steps are wrong. For cases written from what Certyn actually saw, ask for an explore run instead.
  • Word files (.docx) are not accepted. Save the document as PDF, or paste the text.
  • A test case run has 5 minutes. Keep each case to one behaviour.
  • Reading Jira, Linear or GitHub issues needs that tracker connected.
PreviousReproduce a Customer's Bug Report from Support, with Steps and EvidenceNextTest Your API from Its OpenAPI Spec