concourse/topgun
Rui Yang 39b0f8eec9
Merge pull request #8889 from concourse/fix-topgun-k8s-test
Fix compilation error in topgun/k8s test
2024-01-22 11:11:50 -05:00
..
both chore: unnecessary use of fmt.Sprintf or fmt.Sprint 2023-07-06 16:15:05 +08:00
certs move everything under ./topgun 2018-10-23 10:51:14 -04:00
common refactor: move from io/ioutil to io and os packages 2023-06-18 16:54:49 +08:00
core refactor: move from io/ioutil to io and os packages 2023-06-18 16:54:49 +08:00
deployments parameterize stemcell name in topgun test 2022-04-28 12:06:13 -04:00
k8s Merge pull request #8889 from concourse/fix-topgun-k8s-test 2024-01-22 11:11:50 -05:00
operations topgun gc_interval to gc.interval 2023-09-25 15:27:03 -04:00
pcf refactor: move from io/ioutil to io and os packages 2023-06-18 16:54:49 +08:00
pipelines update test to match behaviour 2022-04-06 16:28:20 -04:00
runtime test: update references to use ginkgo/v2 2023-03-10 17:33:13 -05:00
tasks re-enable k8s dns proxy test 2021-04-20 16:55:03 -04:00
vault move everything under ./topgun 2018-10-23 10:51:14 -04:00
.gitignore tsa: don't drain connection when landing/retiring 2018-11-06 17:10:46 -05:00
README.md move everything under ./topgun 2018-10-23 10:51:14 -04:00
exec.go test: update references to use ginkgo/v2 2023-03-10 17:33:13 -05:00
fly.go refactor: move from io/ioutil to io and os packages 2023-06-18 16:54:49 +08:00

README.md

TOPGUN

This suite is one level above Testflight in the sense that it will target a BOSH deployment and make changes to the cluster. This is to test things like workers disappearing, being recreated, etc.

Test Boundaries

Do

  • Configure pipelines, run tasks, etc. - same as Testflight.
  • Make changes to the BOSH deployment.
  • Target the Garden/Baggageclaim APIs to verify container/volume presence.
  • Mutate a VM (network partition, data corruption). These can happen in the real world. Just make sure these get cleaned up after.
  • Pretend you're an operator - prefer fly over API use.

Don't

  • Modify the database directly. It's unrealistic to expect arbitrary SQL queries to have run against the database. Try to force scenarios using the above-defined surface area.
  • Only use DB queries to verify state as a last resort, and replace these with fly commands once we bubble up enough information.