Beginning Facebook Game Apps Development

User Testing

After you have the code in a form that you believe is reasonably free of bugs, it is time to get someone to sit down and use it. More than likely your users will find some issues that you had not expected, or try something that just doesn't make sense. This is particularly true in web applications where the different rendering engines in web browsers handle CSS and JavaScript slightly differently. Compounding this are plugins that actually inject (e.g., Greasemonkey) code into yours, or remove certain elements (e.g., noScript). To paraphrase Marco Arment, these aren't necessarily issues with your code, but they are your problem. It can be a slow, sometimes frustrating, process working through some of the issues that arise from your ...