2026-07-23 11:06:01 +01:00
|
|
|
# tests-e2e — logos-delivery API/e2e tests (Python)
|
|
|
|
|
|
|
|
|
|
End-to-end tests for `liblogosdelivery`, driven through the Python bindings (C-FFI).
|
|
|
|
|
Migrated from [`logos-delivery-interop-tests`](https://github.com/logos-messaging/logos-delivery-interop-tests) (the wrapper / send-API suite).
|
|
|
|
|
|
|
|
|
|
## Layout
|
|
|
|
|
|
|
|
|
|
- `src/` — test framework (node wrappers, steps, helpers)
|
|
|
|
|
- `tests/wrappers_tests/` — the API/e2e scenario tests (`test_s02…s31`)
|
|
|
|
|
- `vendor/logos-delivery-python-bindings/waku/wrapper.py` — CFFI binding (`NodeWrapper`); it `dlopen`s `../lib/liblogosdelivery.so`
|
|
|
|
|
|
|
|
|
|
## Run locally
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
# 1. Build the shared library and place it where the binding looks for it
|
|
|
|
|
./tests-e2e/scripts/prepare_lib.sh
|
|
|
|
|
|
|
|
|
|
# 2. Python env + deps
|
|
|
|
|
python -m venv .venv && source .venv/bin/activate
|
|
|
|
|
pip install -r tests-e2e/requirements.txt
|
|
|
|
|
|
|
|
|
|
# 3. Run (from tests-e2e/)
|
|
|
|
|
cd tests-e2e
|
test(e2e): port remaining wrapper tests from the interop repo (#4077)
* test(e2e): port remaining wrapper tests from the interop repo
The wrapper suite that moved into tests-e2e (#4027) was a reworked subset of
the one still living in logos-delivery-interop-tests. Comparing both sides
showed 21 tests here against 46 there, with no overlap in the delta: the 25
missing tests cover scenarios the reworked set never included.
Ports those 25 tests, bringing the in-repo suite to the full 46:
- 12 send scenarios: s01 (nil/destroyed handle), s03, s04, s05, s11, s13,
s16, s18 (both orderings), s25, s29
- 7 channel lifecycle tests (rc01-rc04)
- 6 wrapper corner cases: auto port allocation, MyBoundPorts, ENR
Supporting changes the ported tests need:
- wrapper_helpers: get_node_tcp_port, get_node_bound_ports, enr_udp_port
- WrapperManager: channel_create/send/close, destroy_keep_ctx
- vendored binding refreshed to the revision exposing the channel API
(additive only; cffi resolves symbols lazily, so nothing existing moves)
Two Edge senders were fixed while porting. build_node_config defaults relay
and store to True, and the flat-JSON config path applies mode=Edge before
explicit fields, so those defaults win: the Edge nodes in s11/s16/s25 came up
as relay and store servers and exercised the relay path instead of lightpush.
They now set relay=False and store=False, matching test_send_e2e_part2. s16
also dropped lightpush=True, which mounts the lightpush server and fails node
start once relay is off; the lightpush client mounts unconditionally.
Suite goes from 21 to 46 functions (53 collected). The docker subset grows
from 3 to 5 as s11 and s25 need a store peer. Local run against a freshly
built library: 45 passed, 2 skipped, 1 xfailed.
* test(e2e): enable autosharding in the channel lifecycle tests
channel_create subscribes to the channel's content topic since #4081, and
resolving that topic to a shard needs autosharding. build_node_config leaves
numShardsInNetwork at 0 and cluster 198 has no preset, so these nodes came up
with static sharding and every channel_create failed with "autosharding is not
configured; pass an explicit shard".
Adds numShardsInNetwork=1 to the six tests that create a channel, matching what
every other wrapper test that touches the send or channel API already does.
rc02 is left alone: channel_send rejects on the id lookup before any shard is
resolved.
Verified locally against a fresh build: the five tests that complete now pass
and the error string is gone from the run.
2026-08-10 08:36:28 +01:00
|
|
|
pytest tests/wrappers_tests -m "not docker_required" # 48 pure-binding tests
|
|
|
|
|
pytest tests/wrappers_tests -m docker_required # 5 tests that also need a Docker nwaku peer (S11/S19/S20/S25/S31)
|
2026-07-23 11:06:01 +01:00
|
|
|
```
|
|
|
|
|
|
|
|
|
|
## CI
|
|
|
|
|
|
|
|
|
|
`.github/workflows/e2e-api-tests.yml` (called from `ci.yml`, `needs: build`) downloads the
|
|
|
|
|
`liblogosdelivery` artifact produced by the `build` job and runs the non-docker subset on every PR —
|
|
|
|
|
so a protocol change and its e2e test land in the same PR.
|