[DO NOT MERGE] Add tests for process instances#1824
Open
philippthun wants to merge 1 commit intodevelopfrom
Open
[DO NOT MERGE] Add tests for process instances#1824philippthun wants to merge 1 commit intodevelopfrom
philippthun wants to merge 1 commit intodevelopfrom
Conversation
philippthun
changed the title
Member
Author
|
This PR can only be merged once CAPI 1.226.0 has been released. |
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.
Are you submitting this PR against the develop branch?
Yes 🫡
What is this change about?
New tests for a new v3 endpoint and parameter.
Please provide contextual information.
See cloudfoundry/cloud_controller_ng#4796.
What version of cf-deployment have you run this cf-acceptance-test change against?
v54.6.0
Please check all that apply for this PR:
Did you update the README as appropriate for this change?
If you are introducing a new acceptance test, what is your rationale for including it CATs rather than your own acceptance test suite?
The data shown by the new endpoint / parameter is coming from Diego through a newly introduced interface. Thus testing the full integration seems reasonable.
How many more (or fewer) seconds of runtime will this change introduce to CATs?
? (2 app pushes)
What is the level of urgency for publishing this change?
Tag your pair, your PM, and/or team!
@jochenehret