uagent-testkit 0.1.1__tar.gz → 0.1.2__tar.gz

uagent_testkit-0.1.2/.github/workflows/ci.yml

@@ -0,0 +1,33 @@
+name: tests
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: pip install -e ".[test]"
+      - run: pytest -q
+
+  oldest-uagents:
+    # The floor pyproject.toml declares, so a wrong floor fails here rather than
+    # for a user pinned to it. uagents 0.23.0 requires uagents-core>=0.4.0.
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: pip install -e ".[test]" "uagents==0.23.0" "uagents-core==0.4.0"
+      - run: pytest -q

uagent_testkit-0.1.2/CHANGELOG.md

@@ -0,0 +1,89 @@
+# Changelog
+
+## 0.1.2 (unreleased)
+
+Fixes from a bug hunt on 2026-10-05, run against uagents 0.26.0 (released 2026-10-02)
+and web3 7.16 and 8.0. Each code fix comes with a test that fails on 0.1.1.
+
+- **ChainDouble works with web3.py.** 0.1.x said it did and never had: every
+  `Web3.HTTPProvider` call failed with `TypeError: '_Response' object does not support
+  the context manager protocol`, every `AsyncHTTPProvider` call with
+  `AttributeError: '_Response' object has no attribute 'read'`, and httpx's
+  `raise_for_status()` raised `RuntimeError`. The double now answers with real
+  `requests` and `httpx` responses and a complete aiohttp one, and the suite drives both
+  web3.py providers.
+- **No unclosed event loops.** The pytest plugin loads into every suite in an
+  environment where the package is installed. It made a new event loop for every test
+  and closed none, so any suite with async tests run under `-W error` failed on
+  `ResourceWarning: unclosed event loop`, even one that never imports uAgents. It now
+  keeps one loop for the session and closes it at the end.
+- **Agents build in any fixture.** A module- or session-scoped fixture that builds an
+  `Agent` failed with `RuntimeError: There is no current event loop` when it was set up
+  after an async test (pytest-asyncio 1.x unsets its loop after each one), and an agent
+  built at import time in a `conftest.py` warned, which `-W error` turns into a failed
+  conftest. The plugin now puts a loop in place before every test's fixtures and before
+  conftests load.
+- **A refusal the handler catches still fails the delivery.** Agents wrap RPC reads in
+  `try/except`, which turned a missing stub back into a silent pass. `deliver()`,
+  `tick()`, `startup()` and `shutdown()` now re-raise any refusal the handler's own work
+  made, in the handler, in tasks it starts or in a thread; `chain.refusals` lists them
+  all. A refusal is matched to its delivery by context, so the agent's own manifest
+  upload and a delivery running alongside are not blamed on the handler.
+- **ChainDouble blocks what it says it blocks.** Eight request paths reached the
+  network: requests' `Session.send()` and adapters, httpx's `Client.stream()`,
+  `Client.send()` and `AsyncClient.send()`, and urllib. requests, httpx, aiohttp and
+  urllib are now patched where every request through them passes. A JSON body that is
+  not JSON-RPC, such as an LLM or webhook call, raised
+  `UnstubbedCall: handler called None` instead of `NetworkCallBlocked`. `http.client`,
+  `urllib3` used directly and raw sockets are not covered, and the README says so.
+- **Dependency floor.** `uagents>=0.22` was wrong: on every 0.22.x the first
+  `deliver()` raises `TypeError`, because `AgentRepresentation` takes no `prefix` before
+  0.23. The floor is now `uagents>=0.23`, and CI tests it.
+- **Reply contracts match the framework.** An `ErrorMessage` answer honours any
+  `replies=` declaration, as the framework's `validate_replies()` allows; the harness
+  used to fail it. And the harness now runs `validate_replies()` after each handler, as
+  `Agent._handle_message` does, so a missing reply logs the same error as in production
+  and `assert_no_errors()` fails on it.
+- **AgentNetwork keeps one session per conversation.** Each hop got a fresh
+  `ctx.session`; in production a reply carries the session of the message it answers.
+  `send()` also takes `session=`.
+- **Sending to an agent outside the network raises `KeyError`.** It returned an empty
+  transcript that passed `assert_all_delivered()`.
+- **Checksummed calldata.** A mixed-case holder or selector in `eth_call` data raised
+  `UnstubbedCall` ("which the test never set") for a balance the test had set.
+- **`raise_errors=False` no longer swallows cancellation.** A timeout around
+  `deliver()` returned a `Delivery` holding `CancelledError` instead of timing out.
+- **`ctx.send_and_receive()` fails loudly.** It returned `None` after no wait at all;
+  it now raises `NotImplementedError` and says why, and fails the delivery even when the
+  handler catches it.
+- **Docs.** The README's "Asserting on failure" example raised `IndexError`.
+  `h.tick()` also runs `@on_schedule` handlers on uagents 0.26+. `include(proto,
+  publish_manifest=True)` uploads a manifest to Agentverse whenever the agent's loop
+  runs, harness or not. `test_storage_does_not_touch_disk` could not see the file it
+  guards against.
+- `LICENSE` holds the full Apache-2.0 text. It held only the short notice, and GitHub
+  listed the licence as "Other".
+
+### Behaviour changes that can fail a test that passed on 0.1.1
+
+In each case the old pass was hiding something:
+
+- A handler that catches an `UnstubbedCall` or `NetworkCallBlocked` now fails its
+  delivery. It passed on data the test never set up.
+- `assert_no_errors()` fails when a handler sends none of its declared replies, which
+  production logs as an error.
+- `AgentNetwork.send()` to an agent never added raises `KeyError`. Nothing was
+  delivered, and the empty transcript passed `assert_all_delivered()`.
+- `ctx.send_and_receive()` raises `NotImplementedError`, caught or not. The handler got
+  `None` even when the peer answered, so only its no-reply path ever ran.
+- Requests through urllib, httpx's `stream()`/`send()` and requests' `Session.send()`
+  are answered or refused under `ChainDouble.install()`. They reached the network.
+
+## 0.1.1 (2026-07-28)
+
+- `ChainDouble`, for agents that read BNB Chain.
+
+## 0.1.0 (2026-07-28)
+
+- First release: the single-agent harness, `AgentNetwork`, Protocol-based agents and
+  the shared chat protocol, and the pytest fixtures.

uagent_testkit-0.1.2/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

{uagent_testkit-0.1.1 → uagent_testkit-0.1.2}/PKG-INFO

@@ -1,10 +1,11 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: uagent-testkit
-Version: 0.1.1
+Version: 0.1.2
 Summary: Test Fetch.ai uAgents offline — handlers, agent-to-agent flows, and BNB Chain reads.
 Project-URL: Homepage, https://github.com/pgalyen1987/uagent-testkit
 Project-URL: Repository, https://github.com/pgalyen1987/uagent-testkit
 Project-URL: Issues, https://github.com/pgalyen1987/uagent-testkit/issues
+Project-URL: Changelog, https://github.com/pgalyen1987/uagent-testkit/blob/main/CHANGELOG.md
 Author-email: Patrick Galyen <pgalyen87@gmail.com>
 License-Expression: Apache-2.0
 License-File: LICENSE
@@ -19,12 +20,14 @@ Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
 Classifier: Topic :: Software Development :: Testing
 Requires-Python: >=3.10
-Requires-Dist: uagents>=0.22
+Requires-Dist: uagents>=0.23
 Provides-Extra: test
 Requires-Dist: aiohttp>=3.9; extra == 'test'
+Requires-Dist: httpx>=0.27; extra == 'test'
 Requires-Dist: pytest-asyncio>=0.24; extra == 'test'
 Requires-Dist: pytest>=8.0; extra == 'test'
 Requires-Dist: requests>=2.31; extra == 'test'
+Requires-Dist: web3>=7; extra == 'test'
 Description-Content-Type: text/markdown
 
 # uagent-testkit
@@ -66,14 +69,16 @@ records instead of transmitting. No sockets, no registration, no waiting.
 - **Handler exceptions are raised** rather than contained into a log.
 - **Storage is in-memory**, so state doesn't leak between tests via the JSON file the
   stock `KeyValueStore` writes to your working directory.
-- **Reply contracts are enforced** — if `@on_message(replies=Pong)` doesn't send a
-  `Pong`, that's an assertion failure instead of a log line nobody reads.
+- **Reply contracts are checked** — if `@on_message(replies=Pong)` sends neither a
+  `Pong` nor an `ErrorMessage`, `assert_reply_contract()` fails, and the error the
+  framework would log lands in `result.logs`, where `assert_no_errors()` sees it.
 - **Interval and lifecycle handlers run on demand**, so an `@on_interval(period=3600)`
   is testable without waiting an hour.
 - **Multi-agent conversations replay deterministically**, with a loop guard instead of
   a hung test.
 - **Agents that read BNB Chain are testable offline** — `ChainDouble` answers BEP-20
-  and balance queries from state your test sets, and blocks any other outbound HTTP.
+  and balance queries from state your test sets, and blocks any other request made
+  through requests, httpx, aiohttp or urllib.
 
 ## Install
 
@@ -81,7 +86,7 @@ records instead of transmitting. No sockets, no registration, no waiting.
 pip install uagent-testkit
 ```
 
-Requires Python 3.10+ and `uagents>=0.22`. The pytest fixtures register automatically.
+Requires Python 3.10+ and `uagents>=0.23`. The pytest fixtures register automatically.
 
 ## Testing one agent
 
@@ -121,11 +126,12 @@ async def test_ping():
 async def test_bad_input_is_handled():
     result = await h.deliver(Ping(text=""), raise_errors=False)
     assert isinstance(result.error, ValueError)
-    assert "empty" in result.logs.errors[0]
+    assert "empty" in str(result.error)
 ```
 
 By default `deliver()` re-raises whatever the handler raised, so a broken handler fails
 the test loudly. Pass `raise_errors=False` when the failure is the thing under test.
+Cancellation and `KeyboardInterrupt` are not handler failures, so they always propagate.
 
 ### Sender verification
 
@@ -146,6 +152,7 @@ async def test_strict_handler_refuses_users():
 ```python
 await h.startup()                  # runs @on_event("startup") handlers
 result = await h.tick()            # runs @on_interval handlers once, ignoring period
+                                   # (and @on_schedule ones, on uagents 0.26+)
 result = await h.tick(only="heartbeat")   # just one, by function name
 await h.shutdown()
 ```
@@ -165,8 +172,11 @@ async def test_conversation():
 ```
 
 Every reply addressed to another agent in the network is delivered in turn until the
-conversation goes quiet. Messages sent to addresses outside the network are collected on
-`transcript.undelivered` rather than silently dropped:
+conversation goes quiet. As on a live network, a reply carries the session of the message
+it answers, so the whole conversation runs in one `ctx.session` (pass `session=` to choose
+it). Sending to an agent you never added raises `KeyError`. Messages a handler sends to
+addresses outside the network are collected on `transcript.undelivered` rather than
+silently dropped:
 
 ```python
 transcript.assert_all_delivered()   # fails if anything went to an unknown address
@@ -237,12 +247,18 @@ async def test_treasury_agent():
     chain.assert_called("eth_call")
 ```
 
-It patches whichever of `requests`, `httpx` and `aiohttp` are importable, so it works
-whether the agent uses web3.py or raw async HTTP, and it understands web3.py's
-JSON-encoded `data=` body as well as `json=`.
+It patches `requests`, `httpx` and `aiohttp` where they are importable, plus `urllib`,
+at the call every request through them passes, so it works whether the agent uses
+web3.py or raw HTTP; the test suite drives web3.py's `HTTPProvider` and
+`AsyncHTTPProvider` through it. It understands web3.py's JSON-encoded `data=` body as
+well as `json=`. It does not cover `http.client` or `urllib3` used directly, or sockets
+a handler opens itself.
 
 Supported: `eth_call` (BEP-20 `balanceOf`, `symbol`, `name`, `decimals`, `totalSupply`),
-`eth_getBalance`, `eth_getCode`, `eth_blockNumber`, `eth_chainId`, batched requests.
+`eth_getBalance`, `eth_getCode`, `eth_blockNumber`, `eth_chainId`, `net_version`,
+`eth_getTransactionCount`, batched requests. Two of these answer without being told:
+`eth_getCode` returns `0x` (no code) for any address not registered with `add_token()`,
+and `eth_getTransactionCount` always returns 0.
 
 Two deliberate refusals, both of which turn a silent pass into a loud failure:
 
@@ -251,11 +267,21 @@ Two deliberate refusals, both of which turn a silent pass into a loud failure:
 with pytest.raises(UnstubbedCall):
     ...                       # rather than quietly returning zero
 
-# any non-JSON-RPC HTTP from inside a handler
+# any other HTTP from inside a handler: a price API, an LLM, a webhook
 with pytest.raises(NetworkCallBlocked):
     ...                       # rather than hitting a real API in CI
 ```
 
+Agents wrap RPC reads in `try/except` so one bad call can't crash them, and that habit
+would swallow a refusal and turn it back into a silent pass. So `deliver()` (and
+`tick()`, `startup()`, `shutdown()`) re-raises any refusal the handler's own work made,
+caught or not: in the handler, in the tasks it starts, and in `asyncio.to_thread()`.
+Work the handler did not start is not charged to it, such as a delivery running
+alongside it or the manifest upload that `include(proto, publish_manifest=True)` queues.
+A refusal from a thread that carries no context (`loop.run_in_executor()`, a plain
+`Thread`) fails every delivery running at that moment. `chain.refusals` keeps every
+refusal either way.
+
 There's also a `bsc` fixture that gives you an installed double directly.
 
 ## pytest fixtures
@@ -274,7 +300,7 @@ def test_with_fixture(agent_harness, agent_network):
 |---|---|
 | `harness(agent)` | Wrap an agent. Swaps in in-memory storage and merges the internal protocol. |
 | `h.deliver(msg, sender=…, raise_errors=True)` | Route a message to its handler. Returns `Delivery`. |
-| `h.tick(only=None)` | Run `@on_interval` handlers once. |
+| `h.tick(only=None)` | Run `@on_interval` (and `@on_schedule`) handlers once. |
 | `h.startup()` / `h.shutdown()` | Run `@on_event` handlers. |
 | `h.storage` | In-memory store, subscriptable. |
 | `h.handles(Model)` | Whether a handler is registered for a type. |
@@ -282,10 +308,10 @@ def test_with_fixture(agent_harness, agent_network):
 | `Delivery.reply(Model)` | The single reply of that type; raises otherwise. |
 | `Delivery.replies(Model, to=…)` | Replies of that type to the sender; `to=ANY` for any destination. |
 | `user_sender()` | A user (non-agent) address, for `allow_unverified` paths. |
-| `Delivery.error` / `.logs` | Handler exception and captured log records. |
+| `Delivery.error` / `.logs` | Handler exception (or a refusal it caught) and captured log records. |
 | `Delivery.assert_replied_with` / `assert_silent` / `assert_no_errors` / `assert_reply_contract` | Chainable assertions. |
 | `AgentNetwork(*agents)` | Multi-agent network. |
-| `net.send(msg, to=…, sender=…, max_rounds=20)` | Play out a conversation. Returns `Transcript`. |
+| `net.send(msg, to=…, sender=…, max_rounds=20, session=None)` | Play out a conversation in one session. Returns `Transcript`. |
 | `Transcript.of(Model)` / `.to(addr)` / `.undelivered` | Inspect what was exchanged. |
 
 ## Scope
@@ -296,6 +322,20 @@ signing, or on-chain settlement — those are integration concerns and mocking t
 give you false confidence. Keep a thin integration test on a real testnet for those, and
 use this for everything else.
 
+`ctx.send_and_receive()` is not supported. Sends are recorded rather than delivered, so
+no answer can reach the handler that is waiting for one; the harness raises
+`NotImplementedError` rather than hand it `None`, and a handler that catches it still
+fails its delivery.
+
+The harness can't stop work an agent schedules on its own event loop.
+`include(proto, publish_manifest=True)` queues an upload of the protocol's manifest to
+Agentverse, and it runs whenever that loop runs, with or without the harness: for an
+agent built inside an async test, as soon as the test yields to the loop. Pass
+`publish_manifest=False` when you build agents for tests.
+
+The [changelog](https://github.com/pgalyen1987/uagent-testkit/blob/main/CHANGELOG.md)
+lists what each release fixed, and which fixes can fail a test that used to pass.
+
 ## Running the tests
 
 ```bash

{uagent_testkit-0.1.1 → uagent_testkit-0.1.2}/README.md

@@ -37,14 +37,16 @@ records instead of transmitting. No sockets, no registration, no waiting.
 - **Handler exceptions are raised** rather than contained into a log.
 - **Storage is in-memory**, so state doesn't leak between tests via the JSON file the
   stock `KeyValueStore` writes to your working directory.
-- **Reply contracts are enforced** — if `@on_message(replies=Pong)` doesn't send a
-  `Pong`, that's an assertion failure instead of a log line nobody reads.
+- **Reply contracts are checked** — if `@on_message(replies=Pong)` sends neither a
+  `Pong` nor an `ErrorMessage`, `assert_reply_contract()` fails, and the error the
+  framework would log lands in `result.logs`, where `assert_no_errors()` sees it.
 - **Interval and lifecycle handlers run on demand**, so an `@on_interval(period=3600)`
   is testable without waiting an hour.
 - **Multi-agent conversations replay deterministically**, with a loop guard instead of
   a hung test.
 - **Agents that read BNB Chain are testable offline** — `ChainDouble` answers BEP-20
-  and balance queries from state your test sets, and blocks any other outbound HTTP.
+  and balance queries from state your test sets, and blocks any other request made
+  through requests, httpx, aiohttp or urllib.
 
 ## Install
 
@@ -52,7 +54,7 @@ records instead of transmitting. No sockets, no registration, no waiting.
 pip install uagent-testkit
 ```
 
-Requires Python 3.10+ and `uagents>=0.22`. The pytest fixtures register automatically.
+Requires Python 3.10+ and `uagents>=0.23`. The pytest fixtures register automatically.
 
 ## Testing one agent
 
@@ -92,11 +94,12 @@ async def test_ping():
 async def test_bad_input_is_handled():
     result = await h.deliver(Ping(text=""), raise_errors=False)
     assert isinstance(result.error, ValueError)
-    assert "empty" in result.logs.errors[0]
+    assert "empty" in str(result.error)
 ```
 
 By default `deliver()` re-raises whatever the handler raised, so a broken handler fails
 the test loudly. Pass `raise_errors=False` when the failure is the thing under test.
+Cancellation and `KeyboardInterrupt` are not handler failures, so they always propagate.
 
 ### Sender verification
 
@@ -117,6 +120,7 @@ async def test_strict_handler_refuses_users():
 ```python
 await h.startup()                  # runs @on_event("startup") handlers
 result = await h.tick()            # runs @on_interval handlers once, ignoring period
+                                   # (and @on_schedule ones, on uagents 0.26+)
 result = await h.tick(only="heartbeat")   # just one, by function name
 await h.shutdown()
 ```
@@ -136,8 +140,11 @@ async def test_conversation():
 ```
 
 Every reply addressed to another agent in the network is delivered in turn until the
-conversation goes quiet. Messages sent to addresses outside the network are collected on
-`transcript.undelivered` rather than silently dropped:
+conversation goes quiet. As on a live network, a reply carries the session of the message
+it answers, so the whole conversation runs in one `ctx.session` (pass `session=` to choose
+it). Sending to an agent you never added raises `KeyError`. Messages a handler sends to
+addresses outside the network are collected on `transcript.undelivered` rather than
+silently dropped:
 
 ```python
 transcript.assert_all_delivered()   # fails if anything went to an unknown address
@@ -208,12 +215,18 @@ async def test_treasury_agent():
     chain.assert_called("eth_call")
 ```
 
-It patches whichever of `requests`, `httpx` and `aiohttp` are importable, so it works
-whether the agent uses web3.py or raw async HTTP, and it understands web3.py's
-JSON-encoded `data=` body as well as `json=`.
+It patches `requests`, `httpx` and `aiohttp` where they are importable, plus `urllib`,
+at the call every request through them passes, so it works whether the agent uses
+web3.py or raw HTTP; the test suite drives web3.py's `HTTPProvider` and
+`AsyncHTTPProvider` through it. It understands web3.py's JSON-encoded `data=` body as
+well as `json=`. It does not cover `http.client` or `urllib3` used directly, or sockets
+a handler opens itself.
 
 Supported: `eth_call` (BEP-20 `balanceOf`, `symbol`, `name`, `decimals`, `totalSupply`),
-`eth_getBalance`, `eth_getCode`, `eth_blockNumber`, `eth_chainId`, batched requests.
+`eth_getBalance`, `eth_getCode`, `eth_blockNumber`, `eth_chainId`, `net_version`,
+`eth_getTransactionCount`, batched requests. Two of these answer without being told:
+`eth_getCode` returns `0x` (no code) for any address not registered with `add_token()`,
+and `eth_getTransactionCount` always returns 0.
 
 Two deliberate refusals, both of which turn a silent pass into a loud failure:
 
@@ -222,11 +235,21 @@ Two deliberate refusals, both of which turn a silent pass into a loud failure:
 with pytest.raises(UnstubbedCall):
     ...                       # rather than quietly returning zero
 
-# any non-JSON-RPC HTTP from inside a handler
+# any other HTTP from inside a handler: a price API, an LLM, a webhook
 with pytest.raises(NetworkCallBlocked):
     ...                       # rather than hitting a real API in CI
 ```
 
+Agents wrap RPC reads in `try/except` so one bad call can't crash them, and that habit
+would swallow a refusal and turn it back into a silent pass. So `deliver()` (and
+`tick()`, `startup()`, `shutdown()`) re-raises any refusal the handler's own work made,
+caught or not: in the handler, in the tasks it starts, and in `asyncio.to_thread()`.
+Work the handler did not start is not charged to it, such as a delivery running
+alongside it or the manifest upload that `include(proto, publish_manifest=True)` queues.
+A refusal from a thread that carries no context (`loop.run_in_executor()`, a plain
+`Thread`) fails every delivery running at that moment. `chain.refusals` keeps every
+refusal either way.
+
 There's also a `bsc` fixture that gives you an installed double directly.
 
 ## pytest fixtures
@@ -245,7 +268,7 @@ def test_with_fixture(agent_harness, agent_network):
 |---|---|
 | `harness(agent)` | Wrap an agent. Swaps in in-memory storage and merges the internal protocol. |
 | `h.deliver(msg, sender=…, raise_errors=True)` | Route a message to its handler. Returns `Delivery`. |
-| `h.tick(only=None)` | Run `@on_interval` handlers once. |
+| `h.tick(only=None)` | Run `@on_interval` (and `@on_schedule`) handlers once. |
 | `h.startup()` / `h.shutdown()` | Run `@on_event` handlers. |
 | `h.storage` | In-memory store, subscriptable. |
 | `h.handles(Model)` | Whether a handler is registered for a type. |
@@ -253,10 +276,10 @@ def test_with_fixture(agent_harness, agent_network):
 | `Delivery.reply(Model)` | The single reply of that type; raises otherwise. |
 | `Delivery.replies(Model, to=…)` | Replies of that type to the sender; `to=ANY` for any destination. |
 | `user_sender()` | A user (non-agent) address, for `allow_unverified` paths. |
-| `Delivery.error` / `.logs` | Handler exception and captured log records. |
+| `Delivery.error` / `.logs` | Handler exception (or a refusal it caught) and captured log records. |
 | `Delivery.assert_replied_with` / `assert_silent` / `assert_no_errors` / `assert_reply_contract` | Chainable assertions. |
 | `AgentNetwork(*agents)` | Multi-agent network. |
-| `net.send(msg, to=…, sender=…, max_rounds=20)` | Play out a conversation. Returns `Transcript`. |
+| `net.send(msg, to=…, sender=…, max_rounds=20, session=None)` | Play out a conversation in one session. Returns `Transcript`. |
 | `Transcript.of(Model)` / `.to(addr)` / `.undelivered` | Inspect what was exchanged. |
 
 ## Scope
@@ -267,6 +290,20 @@ signing, or on-chain settlement — those are integration concerns and mocking t
 give you false confidence. Keep a thin integration test on a real testnet for those, and
 use this for everything else.
 
+`ctx.send_and_receive()` is not supported. Sends are recorded rather than delivered, so
+no answer can reach the handler that is waiting for one; the harness raises
+`NotImplementedError` rather than hand it `None`, and a handler that catches it still
+fails its delivery.
+
+The harness can't stop work an agent schedules on its own event loop.
+`include(proto, publish_manifest=True)` queues an upload of the protocol's manifest to
+Agentverse, and it runs whenever that loop runs, with or without the harness: for an
+agent built inside an async test, as soon as the test yields to the loop. Pass
+`publish_manifest=False` when you build agents for tests.
+
+The [changelog](https://github.com/pgalyen1987/uagent-testkit/blob/main/CHANGELOG.md)
+lists what each release fixed, and which fixes can fail a test that used to pass.
+
 ## Running the tests
 
 ```bash