Collab implementation tests

Question

mweidner037 opened this issue a year ago · comments

Unit tests for all Collab operations. (We have these for many CRDTs but not all).
Unit tests for saving and loading.
Fuzz tests for Collab operations (do many ops concurrently and check eventual consistency).
Fuzz tests for saving and loading with parallel operations.

mweidner037 · Answer 1 · Fri Mar 31 2023 07:49:12 GMT+0800 (China Standard Time)

#245 adds tests for most CRDT operations, including most interesting concurrent pairs.

Still needs:

Unit tests of every method (especially accessors). See npm run coverage's HTML report.
Event tests
Non-CRDT tests, especially core features like serializers. (Note that crdt's coverage report doesn't count core code, but the crdt tests do exercise a lot of it.)

mweidner037 · Answer 2 · Sat Jul 15 2023 04:49:54 GMT+0800 (China Standard Time)

Tests with multiple messages in the same transaction, to make sure latter ones overwrite the former despite equal causal timestamps. (Esp. CVar, CRichText).