Skip to content

Fix v2.BuildpacksTest for CAPI < 2.209.x #1280

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

Merged
merged 1 commit into from
May 28, 2025
Merged

Conversation

Kehrlann
Copy link
Contributor

  • The tests were too precise in checking the results. Now that the lifecycle property has been introduced in newer CAPI versions, the results are different between CAPI versions.
  • We now only check the basic information we care about in those tests (e.g. does the Buildpack exist given its name, or are the updated fields actually updated).

- The tests were too precise in checking the results. Now that the
  `lifecycle` property has been introduced in newer CAPI versions, the
  results are different between CAPI versions.
- We now only check the basic information we care about in those tests
  (e.g. does the Buildpack exist given its name, or are the updated
  fields actually updated).
@Kehrlann Kehrlann force-pushed the dgarnier/fix-buildpacks-test branch from 3aa86ac to 6b8ca1a Compare May 28, 2025 14:06
@Kehrlann Kehrlann merged commit d87f470 into main May 28, 2025
3 checks passed
@Kehrlann Kehrlann deleted the dgarnier/fix-buildpacks-test branch May 28, 2025 14:11
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