I have Claude implementing features from a spec, running tests, creating a build, and then publishing to TestFlight. All I have to do is verify that the build works once I get the TestFlight notification.
I have found a key is to use end-to-end tests and not unit tests.
This has been working well so far after around 100 pull requests for an app I recently decided to make. So far it’s been good.
Comments
I have Claude implementing features from a spec, running tests, creating a build, and then publishing to TestFlight. All I have to do is verify that the build works once I get the TestFlight notification.
I have found a key is to use end-to-end tests and not unit tests.
This has been working well so far after around 100 pull requests for an app I recently decided to make. So far it’s been good.
It’s free, no subscription.
[1] https://trysojourn.app
I’ve done similar with backend projects utilizing GitHub actions to run tests and publish to staging for verification.