I know you give errors precedence … some errors you need to fix immediately. What if you have an unexpected result in your game that happened maybe only once… and you can’t recreate the error? Is this something to be overly concerned about? Is it reasonable to release your game with an error like that. An error or a errors that happen very infrequently and cannot be recreated.
Thanks!
Depends on what you mean by unexpected result. Does the game continue working, but with some minor annoyance, or does it actually crash? Personally, tracking down crash bugs is always my #1 priority, because a crash is a horrible user experience and leads to a perception of poor quality (and bad reviews). Crashes that happen rarely to you may happen much more often to others, because their devices will be different from yours, and they use the app in a different way.
1.) Play test on multiple devices, different software versions, different screen resolutions. Play testing should be exhaustive, testing all possible situations a user might encounter. Trying your app on your personal mobile device just a few times isn’t really playtesting. You really need to try and break the app.
2.) Identify problems, errors, crashes, bugs.
3.) Determine the degree of concern over these problems.
4.) Fix problems.
5.) Repeat. Fixing a problem could cause a different problem.
For more information, you should read this: http://docs.coronalabs.com/guide/basics/debugging/index.html
Depends on what you mean by unexpected result. Does the game continue working, but with some minor annoyance, or does it actually crash? Personally, tracking down crash bugs is always my #1 priority, because a crash is a horrible user experience and leads to a perception of poor quality (and bad reviews). Crashes that happen rarely to you may happen much more often to others, because their devices will be different from yours, and they use the app in a different way.
1.) Play test on multiple devices, different software versions, different screen resolutions. Play testing should be exhaustive, testing all possible situations a user might encounter. Trying your app on your personal mobile device just a few times isn’t really playtesting. You really need to try and break the app.
2.) Identify problems, errors, crashes, bugs.
3.) Determine the degree of concern over these problems.
4.) Fix problems.
5.) Repeat. Fixing a problem could cause a different problem.
For more information, you should read this: http://docs.coronalabs.com/guide/basics/debugging/index.html