Application testing for social media

Application testing for social media

Are there any testing standards for applications on popular social networks? What types of testing would a new app face before being introduced to users in social media?

    Requires Free Membership to View

    When you register, you'll receive targeted emails designed to keep you informed of the most relevant information on Agile development, application security, testing & QA, software requirements, and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSoftwareQuality.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSoftwareQuality.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

That is an interesting question. The answer seems to be “it varies.” What I mean is that some apps, for example some of the free games that can be found on “fun” sites, may get one level of scrutiny. Other games that are intended to drive ad clicks or hits or external hits (like buying extra options for a game), may get looked at a bit more carefully.

Generally, these seem to get a broad spectrum check of “do no harm” to the user experience. If the user has a problem, typically we don’t want them booted off the site completely or to crash the browser. (Based on some of my wife’s experiences with some of these games, that seems to be the maximum of the test effort.)

Those applications that are driving activity for a specific goal, for example an advertising or participation campaign, tend to get closer scrutiny. This makes sense, no? If a “free game” crashes many (not all) computers, people will react with, “Oh well, it’s free.” 

Applications that are intended to be “features” of the site or network tend to get exercised more rigorously. In these instances, if companies are building campaigns around an application, even a fairly-straightforward (to the user) tool like a calendaring app, you don’t want a negative experience with the software to color the end user’s perception of your site, and hence your company. 

If you are writing applications for use on social networks, you want to make sure that they are “up to snuff” and at least as stable as other applications on the same environment. Like many things on the Web, a phrase I heard some time ago seems good advice for these: “Test Early; Test Often; Fail Cheaply.” Or, if you exercise everything possible, at least what you reasonably can (no, we can’t do complete testing for a lot of reasons) any problems that occur should be fairly minor, and you’ll have a good chance to get them corrected before word of the defect goes viral. 

This was first published in December 2011