<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/4dc27a35953340058f9227638e63ff62&quot; frameborder=&quot;0&quot; width=&quot;1662&quot; height=&quot;1246&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1246</height><width>1662</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1246</thumbnail_height><thumbnail_width>1662</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/4dc27a35953340058f9227638e63ff62-1b4c3fcd0c769ab5.gif</thumbnail_url><duration>229.879</duration><title>Testing Coordinated Group Invitation Flows</title><description>This Loom discusses how to coordinate and test multiple PRs for group membership features. It covers ListGroups, create group, invite new member, and accept group invitation, noting most logic lives in utils-superbase-account-ts and the group invitation flow returns a token. The author describes two testing approaches: a Cucumber scenario that verifies backend invitation-based membership, and a frontend vTest harness that uses Account DS functions to execute the full invitation flow, including create group returning a group ID, accepting the invitation returning null with success, and verifying user 2 is in the group. The main emphasis is on validating the end to end invitation flow before moving on to UX.</description></oembed>