Files
osmaczko 233f50195f test: cover GroupV2 group growth against forks
A forked group keeps reporting a healthy roster, so a growth test that compares member counts walks straight past the split. What the members on either branch cannot do is read each other's posts.

The tests grow a group the way people do, one member at a time and five at a time, and after every add require that every joined member reports the same roster and reads what the others post.

The harness can now be told to keep a client running when it rejects an inbound payload, the way a production client does with `Event::InboundError`, so a split group reports who ended up on which branch instead of stopping at the first rejection.
2026-08-21 09:01:34 +02:00
..
2026-05-19 11:54:54 -07:00

This crate is dedicated to backend integration tests.

Tests can be built using any supplied service implementation. Various implementations are available in the Extensions/components crate.

Running Tests

Integration tests are executed when running cargo test from the workspace folder.

Alternatively they can be executed from any crate, using

cargo test --package integration_tests_core