I came across this video from Brian Greenstone, the president and CEO of Pangea Software. You might remember him from such iPhone games as Enigmo, Cro-Mag Rally, or Bugdom 2.
He’s made a video answering “10,000 ft view” questions about iPhone game development that people who are new to the platform should hear. What he’s saying isn’t revolutionary, but it’s a lot of very good advice in 1 spot.
It isn’t the end of the world if you don’t do it ahead of time, but it does make life slightly easier.
(2) Remember that when you find a bug, you should write a test for the expected behavior BEFORE fixing the bug. “The Rails Way” has a great quote about testing:
“It’s not that Rails encourages you to do test-driven development, it’s that it makes it difficult for you not to do test-driven development.” ~Brian Eng
I’ve interpreted this quote into the following mantra:
“It’s not that rails makes it easy to test, it that it makes you pay when you don’t”.
Finding a bug after creating your test suite just means that you missed a test. Take the opportunity to correct that.
