Demystifying the CATs - Michael Xu & Timothy Hausler, Pivotal
summary
CF Acceptance Tests (CATs) are a Go test suite that validates CF software behavior, not production SLIs, and the repo contains over 20 suites categorized as default, special-deployment, and GA feature suites. Runs use an integration_config JSON, often take 30–90 minutes, and are sped up by parallelism (typical local runs 6–8 nodes, CI 12+ nodes) but hit Diego cell memory and API VM bottlenecks. Example workflow: run a focused suite, deploy a BOSH release change to cloud controller, then run the full suite — the PR passes when all tests go green.
AI-written summary · about
chapters (9)
- 0:00Introduction to CATs
- 1:35Motivation for CATs
- 4:23What are CATs
- 9:04Setting up CATs
- 10:52Choosing test suites
- 13:23Optimizing CATs runs
- 16:58Running CATs in CI
- 18:03Live demo overview
- 24:10Q&A and conclusion
related talks
31m#testedAF: Test All the Things (Not Just Your Units)
28mSensitivity, Precision, and When to Test in Prod
31mPut Your Money Where Your CF Is
30mFrom Fix to Final Release: Continuous Integration and Testing for Diego
56mCypress: Where Automated Acceptance Testing Isn’t Just for QA Anymore
24mSupercharging CI: Test Suite Optimization for Speed, Stability, and Savings
52mTest Like a Cat
57mAdvanced Testing Techniques: Tips from the trenches