@petersykim@svpino each workspace has its own checkout so two agents in different workspaces cant collide on the same file. agents that share a workspace are on the same tree and thats where a worktree per agent helps
@alexndrxc@RoxanaLimban the screens can match while the app is broken underneath so an honest compare still isnt proof. give the run a value it can read back off the screen and assert on.
@PandeyKart27234@audizionunes@arpit_bhayani fresh migrate and seed is the default so failures reproduce. if a test needs realistic data use a scrubbed snapshot. rebuild it after every migration or the agent quietly tests an old schema
@SebastianSzturo@simonbs@steipete xcode cloud already runs ui-test workflows on apple-hosted sims and the app store connect api drives it from any os so an agent can start a run and pull the screenshots back. you cant tap between frames though and a round trip is minutes.
@titouangalopin@scubens the 3 vps were solving a namespace problem. a db name, a rabbitmq vhost and a redis db index per worktree is enough and the extra machines are then just cpu
@audizionunes@PandeyKart27234@arpit_bhayani sqlite can live in the worktree and travel with it. a server db stays outside so you still need a name per worktree and a drop at teardown
@PandeyKart27234@audizionunes@arpit_bhayani same rule for the db. give each session its own database name and point the suite at it so nothing falls back to the shared test db
@getprasannav asking an agent about its own state is the part that breaks. have the run write state as it goes so you read the file instead of asking the model
@audizionunes@arpit_bhayani worktrees split the files but not the runtime. two sessions still land on the same port the same test db and on ios the same booted simulator so give each one its own
@JustinPerea@TobinSouth sims need macos so the generic cloud can't host one. apple's cloud does though, xcode cloud runs a ui test workflow on a real sim and you can kick those runs off from any os through the app store connect api
@hs_llllll signing and testflight never come into it for me since xcode cloud just runs my test builds on hosted sims. one asc api key in three env vars is the whole credential side. the first product link still needs xcode once on a mac
real ios simulator screenshots without a mac. one xcshot command kicks off your ui test on xcode cloud and waits for the run, then pulls the labeled pngs out of the xcresult