When I first heard this term or jargon "In the Wild Testing" , I thought it was some kind of exploratory testing that was done by varied experience users. But this is not what it actually is:

What is In the Wild Testing?

As the QA industry matured, it yielded various schools and methods: manual vs. automated; in-house vs. outsourced; guided vs.exploratory; emulators vs. remote access. In each case, these innovations take place inside the confines of a QA lab, either within the company’s firewall, or halfway around the world

In-the-wild testing, on the other hand, emphasizes the need for companies to test under true real-world environments. Why? Because users consume apps under various conditions, including:

•Adverse, unpredictable and widely varied environments

•Outdated or unexpected browsers, plug-ins and anti-virus

•An ever-growing list of hardware and devices

•Imperfect connectivity (both wi-fi and cellular)

To summarize: The only way to launch apps that consistently work in the hands of users – apps that are functional, reliable, secure and intuitive – is to move a portion of testing into the wild. This means professional testers, with real devices, operating under true real-world conditions.

Model: The easiest route to in-the-wild testing requires a crowdsourced testing model. Using this method, a select group of testers - that meet your exact QA requirements - can review your application and submit real-world bugs and feedback
Source: http://www.inthewildtesting.com/

Go through the website to get a better insight to "In the wild testing"


Popular posts from this blog

XPATH for IE / internet explorer

RPA - Blue Prism, OpenSpan, Automation Anywhere vs UIPath