Record Reference
3 min read
Use this page to check, before you ask, whether Oracle knows about the thing you want. You never need to name any of this in a question.
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 |
As well as each record’s own fields, Oracle knows your custom fields, folders, labels, releases and team members. See What Oracle Is Shown.
Links It Can Follow
Section titled “Links It Can Follow”These let a question reach beyond the record it is about. Oracle checks the linked records for each one, which is how Test cases that have an open defect against them works.
Execution history
Section titled “Execution history”| Link | 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 | leaves out test cases whose run was deleted |
Defects
Section titled “Defects”| Link | 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”| Link | Ask |
|---|---|
| Has test coverage | Requirements with no test coverage |
| Verified by a passing test | Requirements that have tests but nothing passing |
The difference matters: coverage counts the link, verification counts the result.
Requirement links on a test case vs. in a run
Section titled “Requirement links on a test case vs. in a run”A test case shows the requirements it is traced to now. A test case in a run shows the requirements it was traced to when it was added to that run. The two can differ if the tracing changed later.
This decides which question to ask, and the wrong one gives a wrong answer rather than an error:
Failures in release 4.2 per requirementlooks at the test cases inside that release’s runs, which is what you want: those results belong to that release.- Asking the same thing about repository test cases looks at each test case’s most recent result in any run. A test case that failed in an unrelated smoke run but passed in the release you care about would be reported as a failure of that release.
Releases and runs
Section titled “Releases and runs”| Link | 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 executions inside a release |
| Has unassigned work not yet started | Test runs signed off with unassigned work left in them |
Automation and stability
Section titled “Automation and stability”| Link | Ask |
|---|---|
| A CI 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 link the other way round: a CI pipeline really runs the test case, but it isn’t marked as automated.
Settings Records Can Be Asked About Too
Section titled “Settings Records Can Be Asked About Too”You can ask about labels, shared steps, parameters and custom fields like anything else, which makes it easy to tidy up your project’s setup:
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 knows how often it is used, so “nobody uses” is a real condition, not an estimate.
Readiness Figures
Section titled “Readiness Figures”Releases, test runs and release executions also have figures that aren’t stored on the record: the readiness verdict, the reason behind it, the readiness gates that failed, and the execution figures. Oracle calculates them when you ask.
They have their own page: Readiness Questions.