openshift · openshift-merge-bot · Aug 3, 2026 · Jul 28, 2026
diff --git a/docs/content/how-to/ci/triage/presubmit-failures.md b/docs/content/how-to/ci/triage/presubmit-failures.md
@@ -302,4 +302,5 @@ Post in [#forum-ocp-hypershift](https://redhat.enterprise.slack.com/archives/C04
 - [Debugging CI Failures](../v2-testing/debugging.md) — Reading JUnit XML, Ginkgo output, and dump-guests artifacts
 - [V2 E2E Testing Overview](../v2-testing/index.md) — Architecture of the v2 test framework
 - [CI Pipeline Configuration](../v2-testing/ci-pipeline.md) — How presubmit jobs are configured
+- [Test Flow](../v2-testing/test-flow.md) — End-to-end CI sequence, process boundaries, and inter-process communication
 - [Daily CI Health](daily-health.md) — Monitoring periodic and presubmit job health
diff --git a/docs/content/how-to/ci/v2-testing/ci-pipeline.md b/docs/content/how-to/ci/v2-testing/ci-pipeline.md
@@ -82,7 +82,7 @@ The `pre` steps run before tests (setup), `test` steps run the actual tests, and
 
 ## The Four CI Binaries
 
-All v2 CI logic is implemented in Go binaries built from `test/e2e/v2/cmd/` and shipped in the `hypershift-tests` image at `/hypershift/bin/`.
+All v2 CI logic is implemented in Go binaries built from `test/e2e/v2/cmd/` and shipped in the `hypershift-tests` image at `/hypershift/bin/`. For how these binaries fit into the overall CI sequence — process boundaries, parallelism, and inter-process communication — see [Test Flow](test-flow.md).
 
 ### `create-guests`
 

diff --git a/docs/content/how-to/ci/v2-testing/debugging.md b/docs/content/how-to/ci/v2-testing/debugging.md
@@ -1,6 +1,6 @@
 # Debugging CI Failures
 
-This guide explains how to diagnose failing v2 CI jobs by tracing test failures to their source clusters and reading diagnostic artifacts.
+This guide explains how to diagnose failing v2 CI jobs by tracing test failures to their source clusters and reading diagnostic artifacts. For background on the overall CI pipeline sequence and process boundaries, see [Test Flow](test-flow.md).
 
 ## Finding Test Results
 

diff --git a/docs/content/how-to/ci/v2-testing/index.md b/docs/content/how-to/ci/v2-testing/index.md
@@ -72,6 +72,8 @@ flowchart TD
 5. **dump-guests** collects diagnostic artifacts in parallel. Always exits 0.
 6. **destroy-guests** tears down all clusters in parallel. Exits non-zero if any destroy fails.
 
+For the complete end-to-end sequence — including process boundaries, inter-process communication, and Ginkgo lifecycle details — see [Test Flow](test-flow.md).
+
 !!! info "Key insight"
     `run-tests` doesn't run tests itself — it invokes the same compiled `bin/test-e2e-v2` binary multiple times with different label filters and cluster targets.
 

diff --git a/docs/content/how-to/ci/v2-testing/test-flow.md b/docs/content/how-to/ci/v2-testing/test-flow.md
diff --git a/docs/content/reference/aggregated-docs.md b/docs/content/reference/aggregated-docs.md
diff --git a/docs/content/reference/e2e-v2-test-flow.md b/docs/content/reference/e2e-v2-test-flow.md
diff --git a/docs/mkdocs.yml b/docs/mkdocs.yml
@@ -108,6 +108,7 @@ nav:
       - 'Writing V2 Tests': how-to/ci/v2-testing/writing-tests.md
       - 'CI Pipeline Configuration': how-to/ci/v2-testing/ci-pipeline.md
       - 'Debugging CI Failures': how-to/ci/v2-testing/debugging.md
+      - 'Test Flow': how-to/ci/v2-testing/test-flow.md
       - 'Migrating from V1': how-to/ci/v2-testing/migration.md
   - 'Cluster Capabilities': how-to/cluster-capabilities.md
   - 'Common':