Testing on Databricks
BDD steps catalog
Generated catalog of Fabric Experiments Databricks BDD step definitions.
This file is generated by pnpm --filter @fabricorg/databricks-bdd steps:catalog.
It includes unused definitions and serves as Fabric's portable Gherkin contract.
The shipped runner is TypeScript; customers can reuse the wording in another
engine, but Fabric does not ship or require a Python adapter.
| Step expression | Example uses | Definition |
|---|---|---|
a Databricks workspace | 3 | src/steps.ts:123 |
a Lakebase database | 0 | src/steps.ts:129 |
catalog {string} and schema {string} | 0 | src/steps.ts:142 |
a table {string} with: | 2 | src/steps.ts:149 |
a table {string} with schema {string} and rows: | 0 | src/steps.ts:157 |
an empty table {string} with schema {string} | 0 | src/steps.ts:165 |
a table {string} with schema {string} from fixture {string} | 0 | src/steps.ts:173 |
fixture files uploaded to volume {string}: | 0 | src/steps.ts:181 |
service principal {string} with grants: | 0 | src/steps.ts:218 |
I run the SQL: | 4 | src/steps.ts:269 |
I query Lakebase: | 0 | src/steps.ts:281 |
I query table {string} | 0 | src/steps.ts:296 |
I run job {string} | 1 | src/steps.ts:301 |
I submit the job orchestration: | 0 | src/steps.ts:307 |
I start the job orchestration: | 0 | src/steps.ts:323 |
I wait for the current job run | 0 | src/steps.ts:330 |
I cancel the current job run | 0 | src/steps.ts:346 |
I repair failed tasks in the current job run | 0 | src/steps.ts:355 |
I submit notebook {string} | 0 | src/steps.ts:383 |
I run dbt build for {string} | 0 | src/steps.ts:393 |
I start a full refresh of pipeline {string} | 1 | src/steps.ts:403 |
I start a refresh of pipeline {string} | 0 | src/steps.ts:420 |
table {string} has {int} rows | 1 | src/steps.ts:434 |
table {string} contains rows matching: | 1 | src/steps.ts:441 |
table {string} contains exactly: | 1 | src/steps.ts:448 |
table {string} matches golden {string} ordered by {string} | 0 | src/steps.ts:462 |
table {string} matches schema contract {string} | 0 | src/steps.ts:469 |
the result has {int} rows | 1 | src/steps.ts:490 |
the result contains rows matching: | 3 | src/steps.ts:497 |
the result matches golden {string} | 0 | src/steps.ts:512 |
the statement fails with {string} | 1 | src/steps.ts:517 |
the statement fails with permission denied | 0 | src/steps.ts:525 |
no rows were rescued in table {string} | 0 | src/steps.ts:532 |
configured table {string} has at least {int} rows | 0 | src/steps.ts:546 |
no rows were rescued in configured table {string} | 0 | src/steps.ts:559 |
row count of {string} is within {int}% of {int} | 0 | src/steps.ts:572 |
the job run reaches {runState} | 1 | src/steps.ts:585 |
task {string} reaches {runState} | 0 | src/steps.ts:592 |
the job run has {int} tasks | 0 | src/steps.ts:608 |
the pipeline update completes within {duration} | 1 | src/steps.ts:615 |
Behavior-driven testing
Gherkin features for Databricks workloads — one .feature file, two engines, readable by analysts and enforced in CI.
Live artifact checks
Gated suites that assert real Databricks artifacts — SQL warehouses, UC grants, Delta contracts, DLT pipelines, Jobs, Lakebase — and emit audit evidence.