Record Reference
2 min read
You never name any of this in a question. It is here so you can tell, before asking, whether the thing you want is something Oracle knows about.
What You Can Ask About
Section titled “What You Can Ask About”| Records | Ask things like |
|---|---|
| Test cases | High priority test cases in the Checkout folder |
| Requirements | Approved requirements with no test coverage |
| Tasks | Tasks that have not been started |
| Requirements and tasks | All the requirements and tasks |
| Defects | Open critical or blocker defects |
| Releases | Releases that are risky |
| Test runs | Test runs still in progress that are healthy |
| Release executions | Release executions that have stalled |
| Test cases in runs | Test cases in the Smoke run |
| Labels | Labels nobody uses |
| Shared steps | Shared steps in this project only |
| Parameters | Workspace level parameters |
| Custom fields | Which custom fields are required |
Alongside the fields each record stores, your own custom fields, folders, labels, releases and team members are part of the vocabulary — see What Oracle Is Shown.
Connections It Can Follow
Section titled “Connections It Can Follow”These are what make a question able to reach past the record it is about. Each one asks a second question of a second set of records, which is why Test cases that have an open defect against them works at all.
Execution history
Section titled “Execution history”| Connection | Ask |
|---|---|
| Never executed | Test cases that have never been executed |
| Not in any run | Test cases that have never been added to any run |
| Executed recently | Test cases not run in the last 10 days |
| Last result was | ”…that last failed” |
| In a run that still exists | filters out cases whose run was deleted |
Defects
Section titled “Defects”| Connection | Ask |
|---|---|
| Has an open defect | Test cases that have an open defect against them |
| Has a linked defect | any defect, open or closed |
| Open | Open defects |
| Linked to a test case | Defects with no test case linked |
Coverage
Section titled “Coverage”| Connection | Ask |
|---|---|
| Has test coverage | Requirements with no test coverage |
| Verified by a passing test | Requirements that have tests but nothing passing |
The second is the one worth knowing about. Coverage counts the link; verification counts the result.
Releases and runs
Section titled “Releases and runs”| Connection | Ask |
|---|---|
| In a release | Test cases that are in no release |
| Linked to a release | defects raised against one |
| Linked to a run or execution | either kind |
| Linked to a standalone test run | runs outside a release |
| Linked to a release execution | only release-gated ones |
| Has unassigned unstarted work | Test runs signed off with unassigned work left in them |
Automation and stability
Section titled “Automation and stability”| Connection | Ask |
|---|---|
| A pipeline has run it | Automated test cases no pipeline has ever run |
| Flaky | Flaky test cases |
Test cases a pipeline runs that are not marked automated uses the same connection the other way round — real pipeline evidence against a case whose automation status says otherwise.
Settings Records Are Queryable Too
Section titled “Settings Records Are Queryable Too”Labels, shared steps, parameters and custom fields can be asked about like anything else, which makes your project’s configuration auditable:
Labels nobody usesShared steps nobody usesWhich custom fields are requiredCustom fields shown on defectsCustom fields that are not set up in this project
Each of these records carries a real usage count, so “nobody uses” is a genuine condition rather than an estimate.
Computed Signals
Section titled “Computed Signals”Releases, test runs and release executions also carry signals that no field stores — the readiness verdict, the reason behind it, the failed gates, and the execution figures. Oracle works them out when you ask.
They have their own page: Readiness Questions.