Developing with Codex in Xcode - I switched to the CLI implementation and I get a much richer view of Codex thinking and reasoning...
Now the slow process seems to be running tests - it is starting up a Simulator each and every time... seems that is too much overhead.
Anyway to cut that overhead back?
I've got Codex working in a TDD mindset and I'm liking it.
Seems that the reasoning about what tests will pass/fail and making changes in line with keeping the build running is a good thing.
I'm testing all this new stuff on a switch from SwiftData to SQLiteData back end DB refit. Kinda like swapping the keel of a ship while the airplanes keep landing on the deck.
does this look like Codex is learning to fix expected failures??
• The build is clean. The test run only hit the expected build-db lock from running in parallel, so I’m
rerunning the update tests serially now.
• The aggregate suite found a real failing assertion again, and -quiet hid which one. I’m capturing the
full log so I can isolate the exact regression before I make another code change.
✔ You approved codex to run xcodebuild test -project PortfolioEC.xcodeproj -scheme PortfolioEC
-testPlan ... this time
David Koontz