Your social app needs people. Your test session shouldn’t need a group chat to organise it.

Test the interaction between accounts

A single signed-in account cannot show you both sides of an invitation or a private conversation. Set up separate development accounts for a community owner, a member and a newcomer. Give each participant its own goal, then observe what each account can actually see.

• Invite a new member and check that the destination and membership state agree.
• Create a post, reply from another account and inspect the resulting thread.
• Compare a member’s view with a moderator’s view after a role change.
• Join the session yourself and see whether the app stays understandable as activity arrives.

Try this first: a newcomer joins the community

Create three test accounts. Ask the host to welcome a newcomer, ask the newcomer to find the right group and introduce themselves, and ask an existing member to respond. Join as yourself. Check the invitation, the visible membership list and the conversation from each account’s browser. These are suggested scenarios; the controls your app exposes determine what participants can do.

Keep the setup for your next change

Save your cast and login state so you can return to the same roles after changing your app. Give participants specific directions, inspect their screens and pause the session when you find something worth investigating. A saved scenario gives you a starting point, although AI actions are not deterministic.

Where AI participants help

Use Jango for development-time exploration of multi-user flows. Keep deterministic tests for exact assertions and real people for usability research and product feedback. Simulated activity does not prove that people will want to use your community.