Skip to content
SpecurityTalk to sales

Readable security test casesTest cases you can read before a re-test.

Your team writes test cases for each issue in readable markdown, or pastes in a .md file. Read, edit or remove any before a re-test. Escape AI uses them as priority checks.

Four test cases for SPEC-253, written by the team in markdown and editable before a re-test.

How it worksThree steps from finding to verdict.

  1. 01

    Write

    Your team writes test cases for the issue in markdown, or pastes in a .md file.

  2. 02

    Review

    Read every test case. Edit or remove any before a re-test.

  3. 03

    Re-test

    Escape AI uses them as priority checks, and ends with one verdict for the issue.

DetailsYour team’s know-how, in plain markdown.

Per issue

Each issue keeps its own test cases.

Your team writes the checks that matter for an issue in readable markdown, or pastes in a .md file. Read, edit or remove any before a re-test.

  • Readable markdown, per issue
  • Written by your team, or pasted as a .md file
  • Edit or remove any before a re-test
Issue SPEC-261 imported from q3-pentest-report.pdf, page 14, finding 3.2, with 4 test cases written.
During a re-test

Priority checks for the AI.

During a re-test, Escape AI attacks your live app and uses the issue’s test cases as priority checks and bypass ideas. The re-test ends with one verdict for the issue: Reproduced, Not reproduced or Inconclusive. When the issue reproduces, you also get the evidence, a proof-of-concept description, the impact and steps to fix.

  • Used as priority checks and bypass ideas
  • One verdict for the issue, not per test case
  • Evidence and fix steps when the issue reproduces
Re-test verdicts: 9 reproduced, 6 not reproduced, 3 inconclusive.

FAQQuestions about test cases.

Who writes the test cases?

Your team does. Write them for each issue in readable markdown, or paste in a .md file.

Can I edit a test case before a re-test?

Yes. Read every test case, then edit or remove any before a re-test.

Does each test case get its own result?

No. Escape AI uses the test cases as priority checks and bypass ideas; they aren’t run one by one. Each finished re-test ends with one verdict for the issue: Reproduced, Not reproduced or Inconclusive.

Are the test cases used again after a fix?

Yes, in every re-test started with Run or by a merge. Start a re-test with Run on the issue, or turn on re-test on merge so merging the fix’s linked pull request starts one. If the fix didn’t hold, the issue goes back to the team and, by default, its assignees are told.

Start proving your fixesSee a real fix re-tested.

Talk to us, or apply for the pilot. Bring a recent pentest report if you have one.

Choose what we may use. You can change this at any time from the footer.

Cookie preferences