Using AI for Testing in iOS

Hello again, and welcome to module five. My name is Ehab Amer, and I’ll be your instructor for this module too.

In the last module, we implemented the feature together, wrote multiple audit files, and identified what was done well and what was not across different dimensions from the plan itself and from Xcode skills.

You might think that the right thing to do is just tell the agent to fix those issues, which wouldn’t be completely wrong. But how can you make sure that they don’t break again by accident in the future? Or even somehow emphasize that those things are important to be fixed or not to break again.

In this module, you’ll take the lessons from those audits, create a plan for unit tests that gives you clear understanding of what the purpose of each test is, what it checks for, and guards against in the future against future regressions.

If you’re thinking that perhaps you can give the agent the list of audits and fix those and write unit tests, that would work to some level till the agent decides on its own what is important and ends up writing pointless tests, that later on when you’re evolving your app, you end up breaking tests that you have no idea what they are for or why they were there in the first place. That ends up slowing down your progress instead of speeding it up.

In lesson two, you’ll have some fun where agents can have control on your app and assist you testing the app and even debugging. You also need to know that those are not very efficient, but it’s important to have an idea of them, how it works, as they can help you. But do not assume that they can do what you do just as good.

Let’s get started.