3 Commits (fa2893cc874dfaf31387e8c4b76c179783bd0d51)

Author	SHA1	Message	Date
Tyler Goodlet	fa2893cc87	Ensure ctx error-state matches the MTE scenario ... Namely checking that `Context._remote_error` is set to the raised MTE in the invalid started and return value cases since prior to the recent underlying changes to the `Context.result()` impl, it would not match. Further, - do asserts for non-MTE raising cases in both the parent and child. - add todos for testing ctx-outcomes for per-side-validation policies i anticipate supporting and implied msg-dialog race cases therein.	2025-03-24 14:04:51 -04:00
Tyler Goodlet	9dc7602f21	Fix `test_basic_payload_spec` bad msg matching ... Expecting `Started` or `Return` with respective bad `.pld` values depending on what type of failure is test parametrized. This makes the suite run green it seems B)	2025-03-24 14:04:51 -04:00
Tyler Goodlet	07ba69f697	Add basic payload-spec test suite ... Starts with some very basic cases: - verify both subactor-as-child-ctx-task send side validation (failures) as well as relay and raise on root-parent-side-task. - wrap failure expectation cases that bubble out of `@acm`s with a `maybe_expect_raises()` equiv wrapper with an embedded timeout. - add `Return` cases including invalid by `str` and valid by a `None`. Still ToDo: - commit impl changes to make the bulk of this suite pass. - adjust how `MsgTypeError`s format the local (`.started()`) send side `.tb_str` such that we don't do a "boxed" error prior to `pack_error()` being called normally prior to `Error` transit.	2025-03-24 14:04:51 -04:00