Skip to content

Commit 4abe7f0

Browse files
committed
Update README
1 parent b745fb1 commit 4abe7f0

File tree

2 files changed

+3
-1
lines changed

2 files changed

+3
-1
lines changed

README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,7 @@ include_app_syslog_tcp
120120
* `include_deployments`: Flag to include tests for the cloud controller rolling deployments. V3 must also be enabled.
121121
* `include_detect`: Flag to include tests in the detect group.
122122
* `include_docker`: Flag to include tests related to running Docker apps on Diego. Diego must be deployed and the CC API diego_docker feature flag must be enabled for these tests to pass.
123+
* `include_file_based_service_bindings`: Flag to include file-based service binding tests. For details, see [RFC0030](https://github.com/cloudfoundry/community/blob/main/toc/rfc/rfc-0030-add-support-for-file-based-service-binding.md)
123124
* `include_http2_routing`: Flag to include the HTTP/2 Routing tests.
124125
* `include_internet_dependent`: Flag to include tests that require the deployment to have internet access.
125126
* `include_isolation_segments`: Flag to include isolation segment tests.
@@ -358,6 +359,7 @@ Test Group Name| Description
358359
`cnb` | Tests our ability to use cloud native buildpacks.
359360
`detect` | Tests the ability of the platform to detect the correct buildpack for compiling an application if no buildpack is explicitly specified.
360361
`docker`| Tests our ability to run docker containers on Diego and that we handle docker metadata correctly.
362+
`file-based service bindings`| Tests file-based service bindings for a buildpack and a CNB app.
361363
`internet_dependent`| Tests the feature of being able to specify a buildpack via a Github URL. As such, this depends on your Cloud Foundry application containers having access to the Internet. You should take into account the configuration of the network into which you've deployed your Cloud Foundry, as well as any security group settings applied to application containers.
362364
`isolation_segments` | This test group requires that Diego be deployed with a minimum of 2 cells. One of those cells must have been deployed with a `placement_tag`. If the deployment has been deployed with a routing isolation segment, `isolation_segment_domain` must also be set. For more information, please refer to the [Isolation Segments documentation](https://docs.cloudfoundry.org/adminguide/isolation-segments.html).
363365
`route_services` | Tests the [Route Services](https://docs.cloudfoundry.org/services/route-services.html) feature of Cloud Foundry.

cats_suite_helpers/cats_suite_helpers.go

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -115,7 +115,7 @@ const (
115115
)
116116

117117
func FileBasedServiceBindingsDescribe(description string, lifecycle string, callback func()) bool {
118-
return Describe(fmt.Sprintf("[file-based service bindings for %s app]", lifecycle), func() {
118+
return Describe(fmt.Sprintf("[file-based service bindings]", lifecycle), func() {
119119
BeforeEach(func() {
120120
if lifecycle == BuildpackLifecycle && !Config.GetIncludeFileBasedServiceBindings() {
121121
Skip(skip_messages.SkipFileBasedServiceBindingsBuildpackApp)

0 commit comments

Comments
 (0)