You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: design-docs/balanced-call-stack-events-implementation-plan.status.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,9 +38,12 @@
38
38
- Verification: `just dev test` passes end-to-end.
39
39
40
40
### WS4 – Testing & Validation
41
-
-**Status:** Not started.
41
+
-**Status:**_In progress_
42
+
- Added Python integration tests covering generator yield/resume sequences, `g.throw(...)` exception injection, coroutine awaits (`asyncio.run`) and plain exception unwinds to verify balanced call/return pairs and recorded payloads.
43
+
- The new coverage exercises the trace JSON to assert call counts, argument capture (including the synthetic `exception` arg), and recorded return values for unwind paths.
44
+
- TODO: extend coverage to async `send()`/`throw()` scenarios and consider rust-side assertions for the integration print tracer if further confidence is needed.
42
45
43
46
## Next Checkpoints
44
-
1.Expand WS4 coverage per plan (async awaits, throw/resume, unwind) and update rust/python integration tests accordingly.
45
-
2.Add rust-side assertions (e.g., `print_tracer`) to validate the expanded event mask.
46
-
3.Document any telemetry updates or metadata changes before shipping the feature.
47
+
1.Extend WS4 coverage to additional async edge cases (e.g., `send()`/`throw()` on coroutines) and consider verifying `print_tracer` output in Rust.
48
+
2.Document any telemetry/logging updates before shipping the feature.
49
+
3.Prepare release notes / changelog once WS4 closes out.
0 commit comments