Describe the change and why it's needed.
Include any links to other PRs, stories, slack discussions, etc... that will help establish context.
- introduces a new test (see *Note below)
- changes an existing test
- introduces a breaking change (other users will need to make manual changes when this change is released)
*Note: We want to keep cf-smoke-tests as lean as possible. The suite's purpose is to reveal fundamental problems with a foundation after initial or upgrade deployment. If your new test is executing anything more sophisticated than validating core functionality of Cloud Foundry, CF Acceptance Tests (CATs) may be more suitable home for it (although CATs are designed to be run as part of a development pipeline and not against production environments).
- YES
- N/A
Something brief that conveys the change and is written with the component author AND CF operator audience in mind.
- Urgent - unblocks current or future work
- Slightly Less than Urgent
It's helpful to tag a few other folks on your team or your team alias in case we need to follow up later.