Skip to main content

Test case review

Test Case Review is the library seen through one question: which of these did an assistant write, and has a person read it yet?

Why it exists​

Sekee lets an AI assistant create test cases through the AI connector. That is useful and it is also exactly the kind of thing that quietly fills a library with plausible, unexamined content. A case written by a model and never read by anybody is not coverage; it is the appearance of coverage, which is worse than a gap because nobody goes looking for it.

The Review screen is where that gets settled.

Using it​

The screen lists cases needing review, with the same toolbar and filters as the rest of the app. Open one, read it, and either accept it or edit it into shape. Reviewing is an ordinary edit — there is no separate approval object — so the case simply stops being unreviewed.

Cases written by a person are not queued for review. This is about the ones where the author was a model.

What to look for​

  • Does it test what it says it tests? Models write plausible steps for the wrong feature more often than they write nonsense.
  • Are the negative cases real? "Enter an invalid email" is a scenario; "enter an email with a leading dot" is a test.
  • Is it linked to a requirement? An unlinked case leaves its requirement reading as uncovered — the traceability page's whole point, reported wrong, by the tool that was supposed to fill it in. The default AI rule asks assistants to link them; this is where you find out whether it did.