experimental/bundletest: add developer testing workflow - #6646
Draft
Sankalp-Mittal wants to merge 7 commits into
Draft
experimental/bundletest: add developer testing workflow#6646Sankalp-Mittal wants to merge 7 commits into
Sankalp-Mittal wants to merge 7 commits into
Conversation
Sankalp-Mittal
added this pull request to stack #6604
September 11, 2026 14:57
Collaborator
Integration test reportCommit: 9af4a1c
Top 4 slowest tests (at least 2 minutes):
|
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.
Changes
Add
databricks bundle test, starter generation, local-support reporting, changed-resource selection, and actionable job-run failures to the experimental BundleTest framework. Resolve inspected configuration through the CLI's offline bundle engine, including multi-file bundles. Include a reproducible 90-second hackathon demo and voiceover transcript.Why
Bundle wiring and data-contract bugs currently surface only after deployment and compute startup. This gives bundle authors a fast pytest workflow locally while preserving the same tests for full-fidelity cloud runs.
Tests
uv run --extra dev pytest -p no:cacheprovider -q— 107 passed, 1 skippeduv run ruff check .— passeduv run ruff format --check .— passedgo test ./cmd/bundle— passedCloud execution was not run because it requires an explicitly selected Databricks profile and workspace compute.
This PR was written with Codex and Claude Code.