Revamp test suite for TwoFac (Kotlin Multiplatform) with parallel sub-agents
Session from pi-coding-sessions on Hugging Face by championswimmer · MIT · condensed by Coders Talk
Click a segment to jump to that moment
6msession
1interventions
GOAL
Review and revamp tests across sharedLib, composeApp, cliApp and other TwoFac modules: drop trivial tests, add tests for complex flows, and coordinate the work across parallel sub-agents via a messenger system.
- +0Prompt · +0Revamp testing: drop obvious tests, add tests for real flows, spin up parallel sub-agents (cli, compose, android, ios, watch) coordinating via messenger, write a plan file, mock sync coordinators/backup providers, commit in small pieces.
- +0mAgent did · +0mSet up .agents/plans/29-testing-revamp/master-plan.md, located existing test files across modules, joined the pi_messenger agent mesh, and attempted to generate a coordination plan via the messenger planner.
- +4mFail · +4mThe messenger planner call failed with 'Unknown error' after a long wait, leaving no coordination plan in place.
- +4mIntervention · +4mDeveloper resent the full original task instructions verbatim after the planner failure.Why: The planner just failed silently, so I re-sent the whole task to make sure it restarted properly instead of limping along with a broken plan.
- +4mAgent did · +4mManually recreated the master plan file, rejoined the messenger mesh under a new identity (FastTiger), messaged peer SageUnion to divide work by module, and began reading existing test files (TwoFacLibTest, WatchSyncCoordinatorTest) to find trivial tests to drop.
- +5mAgent did · +5mTried messenger plan/work commands (no active plan found each time), then proceeded manually: rewrote WatchSyncCoordinatorTest.kt to remove a trivial test, committed it as 'test: drop trivial sync coordinator test', and reported progress to peer SageUnion.
- +6mAgent did · +6mRan ./gradlew testDebugUnitTest across modules and attempted to check messenger task list, which again reported no plan found.
- +6mOutcome · +6mOne trivial test removed and committed; full gradle test run kicked off, but the messenger-based multi-agent planning/coordination never successfully produced a working plan.
VERDICT
Next time I'd skip trying to bootstrap the messenger/sub-agent planner up front and just have the agent start reviewing and committing test changes directly, since the planner kept failing or reporting 'no plan found' and ate most of the session. Resending the original task after the planner error was the only thing that got real progress going again, but even then the multi-agent coordination never really worked.