Automated application testing in xcode

Question

I am currently testing an application that I wrote with ios 4. I spent a lot of time looking for memory leaks, and this side of things seems ok

I have a problem where the application seems to be "accidentally" terminated after switching from one view to another. Sometimes this happens after a minute or 2, and sometimes it does not happen at all. Because of this, it is very difficult to determine where the flaw is in my application and under what circumstances, because my observations of what is happening are subjective. It can also be very annoying very quickly, sitting there, pressing buttons, until something happens, and then tries to remember the sequence of your actions.

What would be a good way to track down the cause of this seemingly random problem?

For instance,

I remember talking to a QA engineer before, and he talked about the tools that he used to automate the user through the application. He would leave him to run during the night, and then in the morning he could study what combination of user actions and under what circumstances a problem arose.

Are there such tools for testing iphone apps? Ideally, I would like to see a report

action a

action b

action c

= everything is fine.

action a

action c

action b

= There was a problem.

Answer 1

There is also a fonemonkey: http://www.gorillalogic.com/fonemonkey

As for random crashes ... I am testing, not the developer, but random crashes - this is usually one of the topics that I study in more detail in each iphone application. My favorite scenarios: leave the phone for 2 minutes, for 10 minutes and switch applications (on iOS 4). In all cases, it is better to use a real phone (and the older, the better), and not a simulator (some accidents never happen on a simulator). Common nested views are affected (for example, go to some view, let the phone sleep, press the "Back" button to return to the previous view - failure). Developers usually say that improper save / release, auto-detection, while another object contains a pointer, and other memory problems are to blame. Also, device logs (which will have a crash report) can usually pinpoint the problem fairly accurately.

Answer 2

Hey.
Tools from Apple. Apple link .
Tools have their limitations and disadvantages, but just try. This can be confusing for begging, so try following a tutorial or some others .

Answer 3

Launch the application with zombies turned on . In addition, instruments in Xcode are very useful.