Releases: cloudfoundry/cf-acceptance-tests
Releases · cloudfoundry/cf-acceptance-tests
v2.8.0
Notice:
- this release was marked as a pre-release after initial publish because a leaky credentials bug was exposed.
A new release of CATs will be released once the bug is fixed.
New Tests
-v3/deployment.go
- Promote test out of
capi-experimental
intov3
-- validate zero downtime app deployments.
Updated Tests
-aps/lifecycle.go
- Provide better CATs failure message (the output of
cf app
) if test fails to match the metrics regex.
v2.7.0
v2.6.0
New Tests
logging_isolation_segments/logging_isolation_segments.go
- Tests that the logs from an app running on an isolated Diego cell can be retrieved from the isolated logging system. Your CF deployment must been deployed with a logging isolation segment and this test cannot be run together with the routing_isolation_segments test.
Other Updates
windows/running_security_groups_win.go
- Added windows stack -s windows for CATs.
v2.5.0
New Tests
volume_services/volume_services.go
- Tests that volume service provided by volume service broker can be bound to the app and the app can use the volumes provided by that service. 23a2316
Other Updates
assets/catnip
- updated to fix failing ASG/C2C test when running CATs against newer rootfs. 6c6eaaa
v2.4.0
Updates
ssh/ssh.go
- Add more verbose logging around SSH test
apps/app_stack.go
- Added support for multiple stacks to be passed in via
integration-config.json
- if no
stacks
value is included in the config, default stack is set tocflinuxfs2
- stacks currently supported:
cflinuxfs2
andcflinuxfs3
- if no
- Added support for multiple stacks to be passed in via
v2.3.0
v2.2.0
New Features
- In Development-->
example-cats-config.json
52ef6a0- Although not yet finalized, this config will be maintained as the comprehensive listing of what can be enabled in CATs.
- Used as-is, it will enable the tests we recommend running to provide minimum coverage for your foundation.
- You may wish to transform it programmatically to run/disable tests within your pipeline(s) as appropriate. ref: #332
Updates
v2.1.0
Updates
services/service_instance_lifecycle.go
23981dc- Do not expect service delete to exit 0
The 'delete-service' command issues a command that is async with regards to the broker but not CAPI.
This causes the cli to return a non-zero exit code when the service has an operation in progress.
- Do not expect service delete to exit 0
windows/running_security_groups_win.go
5be910b- Run warm up request after application restarts for windows CATs [finishes #160562352].
assets/python/...
ec57bb0- Modify python fixture app to be multithreaded. #337
v2.0.0
Breaking Change
- Updated the default
credhub_client
tocredhub_admin_client
.- Note: If you're using
cf-deployment-concourse-tasks
v7.6 or greater, your integration config will be fine. Else, you'll need to make a manual update.
- Note: If you're using
Other updates
- Bumped to CredHub 2.0 for CredHub acceptance tests.
windows/running_security_groups_win.go
43f09c8- CAT Failure Fix -- [Top Level] | [windows] | WINDOWS: App Instance Networking | WINDOWS: Using container-networking and running security-groups | WINDOWS: correctly configures asgs
- Added a warm-up request to force HWC to do just-in-time compilation
v1.9.0
Updates
vendor/github.com/cloudfoundry-incubator/cf-test-helpers/workflowhelpers/internal/cf_auth.go
&&
vendor/github.com/cloudfoundry-incubator/cf-test-helpers/workflowhelpers/user_context.go
- added more verbose logging to help diagnose cf-auth flakes (see this story for more context)