-
Notifications
You must be signed in to change notification settings - Fork 125
Refactor initTestTemplate/deployBundle/destroyBundle to not return errors #2017
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
https://github.com/databricks-eng/eng-dev-ecosystem/actions/runs/12348564582 There is TestDashboard failure which seems unrelated. Running CI against main to confirm: https://github.com/databricks-eng/eng-dev-ecosystem/actions/runs/12350231338 |
461cc27 to
7a516c8
Compare
This commit updates all deployBundle calls in integration tests to remove error handling, reflecting the function's updated signature that no longer returns an error.
refactor: Update destroyBundle to not return error in bundle tests
…t.Fatal for consistency
83cc0d0 to
577f6a5
Compare
|
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. |
Changes
These test helpers were updated to handle the error internally and not return it. Since they have testing.T object, they can do so directly. On the caller side, this functions were always followed by require.NoError(t, err), that was cleaned up.
This approach helps reduce the setup/teardown boilerplate in the test cases.
Tests
Existing tests.