ABSTRACT
The author explains how to trace some comments in the simulator console. He elaborates and gives some tips to test and debug app like a pro. There are two kinds of bugs: Syntax bugs, and Programming bugs. The syntax bugs are easy to fix, the Corona Simulator will display the error in the console or a dialog box when there is a typo in code. The programming bugs can be tricky to fix, when the simulator does not display a message, but the program is doing weird things: some values are wrong, and the game does not respond. The message from the simulator is quite clear, providing the line number along with some information about the bugs. For a game programmer, bugs are the devil, fixing bugs is the main part of the job. The author takes a close look at how his time is spent when he program, a large part is dedicated to hunting down bugs.
