test(e2e): cover uv setup-local on a serverless target - #2126
Merged
Conversation
rugpanov
had a problem deploying
to
test-trigger-is
August 17, 2026 14:59 — with 
GitHub Actions
Failure
GitHub Actions
Failure
rugpanov
force-pushed
the
test/setup-local-e2e
branch
from
August 17, 2026 15:16
38c5db8 to
04bcdfc
Compare
rugpanov
had a problem deploying
to
test-trigger-is
August 17, 2026 15:19 — with
GitHub Actions
Error
GitHub Actions
Error
rugpanov
marked this pull request as ready for review
August 17, 2026 15:21
Contributor
Author
|
🤖 Integration tests ❌ 2 of 37 test jobs failed for |
rugpanov
force-pushed
the
test/setup-local-e2e
branch
from
August 18, 2026 09:10
04bcdfc to
af65e52
Compare
rugpanov
had a problem deploying
to
test-trigger-is
August 18, 2026 09:11 — with
GitHub Actions
Error
GitHub Actions
Error
Contributor
Author
|
🤖 Integration tests ✅ all 37 test jobs passed for |
rugpanov
force-pushed
the
test/setup-local-e2e
branch
from
August 18, 2026 15:11
af65e52 to
371729b
Compare
rugpanov
had a problem deploying
to
test-trigger-is
August 18, 2026 15:13 — with
GitHub Actions
Error
GitHub Actions
Error
Contributor
Author
|
🤖 Integration tests ❌ 2 of 37 test jobs failed for |
*Why*: * The uv-native "Setup python environment" flow (which shells out to `databricks environments setup-local`) has no end-to-end coverage; the bundled CLI now ships the subcommand, so the full flow is testable. * Guards the main user journey against a real serverless target: initialization, that databricks-connect imports and runs, and that a re-run is idempotent (stays ready, no drift). *What:* * Add `setup_local.ucws.e2e.ts` (serverless/UC shard): opt into the uv feature at Workspace scope, attach serverless + pick the recommended version, run setup-local, verify the `.venv` interpreter and the "Python environment ready" config-view row, run a file with Databricks Connect against the provisioned env, and re-run to assert idempotency. * Assertions gate on filesystem/tree ground truth (not transient toasts) with serverless-cold-start budgets, following the serverless DBConnect spec's approach; the re-run is invoked by command id since it is palette-hidden. *Verification:* * `eslint` and `prettier -c` pass on the new spec. * The spec is auto-discovered by `list_integration_tests.ts` and tagged `ucws` (routed to the serverless-capable workspace); it runs in the eng-dev-ecosystem integration workflow. Co-authored-by: Isaac
rugpanov
force-pushed
the
test/setup-local-e2e
branch
from
August 18, 2026 16:39
371729b to
0f02904
Compare
Contributor
|
If integration tests don't run automatically, an authorized user can run them manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
rugpanov
had a problem deploying
to
test-trigger-is
August 18, 2026 16:40 — with
GitHub Actions
Error
GitHub Actions
Error
Contributor
Author
|
🤖 Integration tests ✅ all 37 test jobs passed for |
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The uv-native Setup python environment flow — which shells out to
databricks environments setup-local— has no end-to-end coverage. The bundled CLI now ships theenvironments setup-localsubcommand, so the full flow is testable against a real serverless target.This adds e2e coverage for the main user journey:
.venvis provisioned.databricks-connectimports and executes without errors).What
packages/databricks-vscode/src/test/e2e/setup_local.ucws.e2e.ts(serverless/UC shard). The spec:Setup python environmentcommand (routes to the uv flow),.venvinterpreter on disk and the persistent "Python environment ready" config-view row,hello.pywith Databricks Connect and checks the output file,databricks-connectinstall fallback, so a broken provision fails the test rather than being masked.Verification
eslintandprettier -cpass on the new spec.scripts/list_integration_tests.tsand taggeducws, so it runs on the serverless-capable workspace in the integration workflow.This pull request and its description were written by Isaac.