Skip to content

Convert TestAbortBind to an acceptance test #3111

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

Closed
wants to merge 3 commits into from

Conversation

anton-107
Copy link
Contributor

@anton-107 anton-107 commented Jun 24, 2025

Changes

  1. Add a step to an existing acceptance test to replace the original TestAbortBind integration test

Why

One change in the series of changes for converting integration tests into acceptance tests.
This will allow for easier testing of various backing solutions for bundle deployment

Tests

Ran cloud and local versions of bundle/deployment/bind/job/job-spark-python-task

Closed this PR, in favor of #3116

@anton-107 anton-107 temporarily deployed to test-trigger-is June 24, 2025 10:06 — with GitHub Actions Inactive
@anton-107 anton-107 marked this pull request as ready for review June 24, 2025 13:01
grep "^Error:" out.bind-result.txt
rm out.bind-result.txt

title "Check that job is not bound and not updated with config from bundle:"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a missing deploy in between the failed bind and the job get.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch! I realized that this needs to be a separate test, created it here: #3116

@pietern pietern requested a review from Copilot June 24, 2025 13:04
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR converts the original TestAbortBind integration test into an acceptance test to improve testing flexibility for different bundle deployment backing solutions.

  • Removed the TestAbortBind integration test from the integration tests.
  • Added new acceptance test steps in the job-spark-python-task acceptance test script and updated the expected output accordingly.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
integration/bundle/bind_resource_test.go Removed the original TestAbortBind integration test.
acceptance/bundle/deployment/bind/job/job-spark-python-task/script Added steps to simulate and verify binding failure without auto-approve and successful binding with auto-approve.
acceptance/bundle/deployment/bind/job/job-spark-python-task/output.txt Updated expected output to match the new acceptance test steps.
Comments suppressed due to low confidence (2)

acceptance/bundle/deployment/bind/job/job-spark-python-task/script:36

  • [nitpick] Consider using a more specific pattern or dedicated assertion method to validate the full error message, which could help ensure that the test detects any unintended changes in the error output.
grep "^Error:" out.bind-result.txt

acceptance/bundle/deployment/bind/job/job-spark-python-task/script:35

  • Consider verifying that the '&>' redirection syntax is supported in all target environments; if compatibility is a concern, replacing it with a POSIX-compliant redirection method may improve portability.
trace errcode $CLI bundle deployment bind foo $JOB_ID &> out.bind-result.txt

@anton-107 anton-107 marked this pull request as draft June 25, 2025 10:19
@anton-107 anton-107 closed this Jun 25, 2025
anton-107 added a commit that referenced this pull request Jun 25, 2025
## Why
<!-- Why are these changes needed? Provide the context that the reviewer
might be missing.
For example, were there any decisions behind the change that are not
reflected in the code itself? -->
One change in the series of changes for converting integration tests
into acceptance tests.
This will allow for easier testing of various backing solutions for
bundle deployment

This is a follow-up of the closed not-merged PR #3111
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants