<testsuites name="Mocha Tests" time="11.863" tests="12" failures="0">
  <testsuite name="Root Suite" timestamp="2025-12-18T18:42:48" tests="0" time="0.000" failures="0">
  </testsuite>
  <testsuite name="realtime/liveobjects" timestamp="2025-12-18T18:42:48" tests="0" time="0.000" failures="0">
  </testsuite>
  <testsuite name="Sync events" timestamp="2025-12-18T18:42:53" tests="12" time="7.256" failures="0">
    <testcase name="realtime/liveobjects Sync events The first ATTACHED should always provoke a SYNCING even when HAS_OBJECTS is false, so that the SYNCED is preceded by SYNCING" time="0.257" classname="The first ATTACHED should always provoke a SYNCING even when HAS_OBJECTS is false, so that the SYNCED is preceded by SYNCING">
    </testcase>
    <testcase name="realtime/liveobjects Sync events ATTACHED with HAS_OBJECTS false once SYNCED emits SYNCING and then SYNCED" time="0.218" classname="ATTACHED with HAS_OBJECTS false once SYNCED emits SYNCING and then SYNCED">
    </testcase>
    <testcase name="realtime/liveobjects Sync events If we&apos;re in SYNCING awaiting an OBJECT_SYNC but then instead get an ATTACHED with HAS_OBJECTS false, we should emit a SYNCED" time="0.185" classname="If we&apos;re in SYNCING awaiting an OBJECT_SYNC but then instead get an ATTACHED with HAS_OBJECTS false, we should emit a SYNCED">
    </testcase>
    <testcase name="realtime/liveobjects Sync events An initial ATTACHED with HAS_OBJECTS true provokes a SYNCING" time="0.180" classname="An initial ATTACHED with HAS_OBJECTS true provokes a SYNCING">
    </testcase>
    <testcase name="realtime/liveobjects Sync events ATTACHED with HAS_OBJECTS true when SYNCED should provoke another SYNCING, because we&apos;re waiting to receive the updated objects in an OBJECT_SYNC" time="0.187" classname="ATTACHED with HAS_OBJECTS true when SYNCED should provoke another SYNCING, because we&apos;re waiting to receive the updated objects in an OBJECT_SYNC">
    </testcase>
    <testcase name="realtime/liveobjects Sync events If we&apos;re in SYNCING awaiting an OBJECT_SYNC but then instead get another ATTACHED with HAS_OBJECTS true, we should remain SYNCING (i.e. not emit another event)" time="0.198" classname="If we&apos;re in SYNCING awaiting an OBJECT_SYNC but then instead get another ATTACHED with HAS_OBJECTS true, we should remain SYNCING (i.e. not emit another event)">
    </testcase>
    <testcase name="realtime/liveobjects Sync events A complete multi-message OBJECT_SYNC sequence after ATTACHED emits SYNCING and then SYNCED" time="0.232" classname="A complete multi-message OBJECT_SYNC sequence after ATTACHED emits SYNCING and then SYNCED">
    </testcase>
    <testcase name="realtime/liveobjects Sync events A complete single-message OBJECT_SYNC after ATTACHED emits SYNCING and then SYNCED" time="0.183" classname="A complete single-message OBJECT_SYNC after ATTACHED emits SYNCING and then SYNCED">
    </testcase>
    <testcase name="realtime/liveobjects Sync events SYNCED is not emitted midway through a multi-message OBJECT_SYNC sequence" time="0.208" classname="SYNCED is not emitted midway through a multi-message OBJECT_SYNC sequence">
    </testcase>
    <testcase name="realtime/liveobjects Sync events A complete multi-message OBJECT_SYNC sequence when already SYNCED emits SYNCING and then SYNCED" time="0.175" classname="A complete multi-message OBJECT_SYNC sequence when already SYNCED emits SYNCING and then SYNCED">
    </testcase>
    <testcase name="realtime/liveobjects Sync events A complete single-message OBJECT_SYNC when already SYNCED emits SYNCING and then SYNCED" time="0.184" classname="A complete single-message OBJECT_SYNC when already SYNCED emits SYNCING and then SYNCED">
    </testcase>
    <testcase name="realtime/liveobjects Sync events A new OBJECT_SYNC sequence in the middle of a sync sequence does not provoke another SYNCING" time="0.231" classname="A new OBJECT_SYNC sequence in the middle of a sync sequence does not provoke another SYNCING">
    </testcase>
  </testsuite>
</testsuites>