docs(core): assertLive gets its section on the testing-harness page (#2075) - #2200
Merged
Conversation
… page #1857's third acceptance item never shipped: PR #1997 added assertLive to the DeployedStack handle and the worked example used it, but touched no docs, so the local-testing/testing-harness page had zero mentions of it. The new "Asserting the deploy is live" section covers the signature, the two call shapes, the three failure modes (observed absent, not observed, foreign marker) and that each throws rather than passes, endpoint resolution being identical to deploy/destroy, and the v1 boundary against deep observation (#1014). The example is lifted from examples/testing-harness-aws/harness.e2e.test.ts, the worked example named in both issues. Fixes #2075. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FoXyD9UvKQ5ZdhiR9JT1yB
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #2075.
#1857 shipped
assertLiveon the testing harness and used it inexamples/testing-harness-aws, but its third acceptance item, a section on the testing-harness page, never landed.grep -rl assertLive docs/src/content/docswas empty.This adds
## Asserting the deploy is livetodocs/src/content/docs/local-testing/testing-harness.mdx, between the API summary and the project requirements, plus a one-lineassertLiveentry in theDeployedStacklist. It covers the two call shapes, the three failure modes and their distinct error types, that "not observed" is never a pass, endpoint resolution matching deploy and destroy, and the v1 boundary of existence and status only. The example is lifted from the real e2e test and links to it.No cross-links were added from the lifecycle or effect-receipts pages, since neither mentions live assertions today.
Gates
The two in-page anchors were checked by hand against their headings; the repo has no local link checker outside the CI lychee run.
🤖 Generated with Claude Code
https://claude.ai/code/session_01FoXyD9UvKQ5ZdhiR9JT1yB