I’ve developing multiple apps and I’ve found Claude invaluable for visual/functionality regression testing without having to setup a programatic integration test. I asked Claude to use an iOS simulator MCP to navigate through every aspect of the app, using both visual clues and knowledge from the source code, to explore every single screen and perform every action possible, and for each screen to take a screenshot and save it, keeping a log of its travels. Then I make a whole bunch of changes, add screens, change font sizes, and have Claude rerun the explore again and it produces a beautiful simple report saying things like: CRITICAL - Clicking reset email address in profile screen now produces an error message. Bug - The text at the bottom of X screen is now cut off. Visual - XYZ screen, when showing ABC now has larger text Functionality - Screen Blah now has an extra button that goes to a new screen. I then consider those changes with respect to the work I’ve done and whether it’s expected. This is a glorious way to do testing. It doesn’t substitute for tests (especially not unit and business logic tests) but it’s way easier for E2E. I just set it up and away it goes. An hour later its explored my entire app. API credits around $25 for about an hours exploring. submitted by /u/Ok-Experience9774
Originally posted by u/Ok-Experience9774 on r/ClaudeCode
You must log in or # to comment.