Testing frameworks.

[richburdon]

We have a complex stack and many different micro-frameworks for testing these. The goal is to create a unified testing framework that is adaptable to isolate different parts of the stack (e.g., network, replication, parties, item/model consistency, etc.) And to create simulations to stress test the system.

Currently https://github.com/dxos/sdk/tree/master/testing/spawn-testing implements the most general testing framework.

For discussion:

• [ ] Deprecate https://github.com/dxos/echo/tree/master/packages/echo-environment-test.
• [ ] Move https://github.com/dxos/sdk/tree/master/testing to new dxos/gravity mono-repo.
• [ ] Evolve https://github.com/dxos/sdk/tree/master/testing/spawn-testing to use same API as bots (@egorgripasov). See https://github.com/dxos/gravity/issues/2
• [ ] Evolve spawn-testing to use common network abstraction as https://github.com/dxos/mesh/tree/master/packages/feed-replication-network (or similar).
• [ ] Use @dxos/gem to visualize tests (and demonstrate them via docs).

[richburdon]

• [ ] https://github.com/dxos/sdk/pull/144 (from sdk)
• [ ] https://github.com/dxos/gravity/pull/4 (to gravity)

[dboreham]

Evolve spawn-testing to use common network abstraction as https://github.com/dxos/mesh/tree/master/packages/feed-replication-network (or similar).

Not trivial due to different layer/semantics for network interaction, see https://github.com/dxos/gravity/issues/8 for discussion. Compatibility the other direction (use NetworkManager everywhere but adapt it to do what feed-replication-network allows, may be the better approach.