Exploratory Testing Tip: Use the wisdom of the crowd

Exploratory testing unleashes the full potential of each and every tester. It trusts them to determine what features, functions, and paths need testing, and to review and document the results on the spot. But how to you get the most out of exploratory testing? How do you get enough experienced and engaged testers checking your app or your website to ensure the kind of coverage required for high-quality software?

Crowdtesting (or crowdsourced testing) is the perfect complement to exploratory testing. By putting dozens or hundreds of testers to work testing your software, you benefit from the “wisdom of the crowd”:

“The wisdom of the crowd is the collective opinion of a group of individuals rather than that of a single expert.”

Each crowdtester checks your app or website based on the exploratory parameters you outline. Instead of using scripted testing’s stringent and restrictive step-by-step test scenarios, you rely on the large number of testers to explore all the different pathways and potential problem areas.

Your software gets the benefit of exploratory testing and the unfettered examination of an experienced software tester, counterbalanced by the security of having a crowd to find all the important bugs.

Exploratory Testing Tip: Out of the lab, into the real world

Exploratory testing has one main goal: breaking testers free from tests scripts and step-by-step action lists, and letting them examine, experiment, and explore software.

Here’s our tip for today:

Take exploration one step further: Get your testers and your software out of the bubble of the testing lab. Break free of the confines of the controlled testing environment. That’s the only way to make sure that your apps and your websites work in real-world conditions.

While your app or software may run smoothly inside the four walls of the office, this doesn’t mean that it works all the time for everyone outside your office. By testing with the crowd, you can also make sure it works where your users are most likely to use the software. This could be at home, at work, on the road, with a spotty internet connection, in rural or urban areas.

Wherever your product team is, your customers will likely be somewhere else. They’ll still expect your software to function, though. Like test driving a car on a real road instead of a simulator, crowd testing puts software in the hands of the target audience under real-life conditions and receiving qualified feedback.

Looking for more exploratory testing tips? Check these posts out

5 Ways To Increase Customer Trust on Your Website

Every time users visit your website, you get the chance to create a long-term relationship with them. One fundamental component of any relationship that underscores this bond is trust. Gaining users’ trust is no simple task, and there are many ways you can lose it.

There’s no one-size-fits-all solution to building customer trust, it depends on what type of website you have and what kind of business you’re running. However, we have put together these five actions you can take to inspire more trust on your website and improve user experiences at the same time. Continue reading “5 Ways To Increase Customer Trust on Your Website”

Exploratory Testing Tip: Cover A Wide Range of Platforms

Exploratory testing empowers testers to engage with the software. They can examine areas, paths, and options based on their experience and learning.

By removing strictures of scripted testing, exploratory testing allows for holistic approach to test design, execution, and analysis.

Testers are empowered in the moment of testing, on the device and platform they’re using. This makes it possible for them to look for all sorts of potential problems and issues, but in particular ones that may be related to what the software is running on, whether it’s a mobile app, a web app, or smartwatch software, or anything else. For example, with a mobile web app, it’s critical to cover as many platforms as possible: mobile web apps run on the many different versions of Android smartphones, they can run on the Chrome mobile browser (on both iOS and Android), they run on mobile Safari and in other apps’ web-views. Continue reading “Exploratory Testing Tip: Cover A Wide Range of Platforms”

How A Mobile Video Platform Does Crowdsourced QA Testing

As one of our first partners based in San Francisco, we’ve always wanted to take the opportunity to sit down with the folks at Tout to find out how their QA team is using test IO in their daily development process.

We had the chance to sit down with both Carl Rivas, QA director at Tout, as well as Derk Pippin, a QA engineer for two different perspectives on how crowdsourced testing integrates into their workflow.

Meet 2016’s Mobile Testing Challenges

Over at Ministry of Testing, Rosie Sherry polled the community for their thoughts on the biggest challenges for mobile testers in 2016. Given the breakneck speed of change in technology, I’d expected to see at least one totally new mobile testing challenge to watch out for, or a big change coming down the pipeline that would force testers and QA teams all over to rethink everything.

Instead, you’ll recognize most of these problems, as they’ve come up before and some have even been discussed on our blog here at test IO. One of them, “in the wild testing,” or as we call it here – real world testing – is the cornerstone of test IO’s testing philosophy and the reason for our existence. Continue reading “Meet 2016’s Mobile Testing Challenges”

What we can learn from the iOS update that bricked iPhones

Lapses in quality assurance can turn ground-breaking innovation into deal-breaking embarrassments. Too many of these lapses will knock an innovator off its spot at the top. An example comes from Apple, a global technology leader known for attention to detail and quality for every aspect of its software and hardware development.

Apple product launches are often anticipated as “The Next Big Thing,” but high expectations have a downside: when the Cupertino giant doesn’t deliver something disruptive or unexpected, the technology press and stock market don’t hold back in their criticism. Continue reading “What we can learn from the iOS update that bricked iPhones”

Let Testers Do Terrible Things to Your Code

Jeff Atwood (you may know him as one of the founders of Stack Exchange) writes about how he learned to test his code:

“I believe a key turning point in every professional programmer’s working life is when you realize you are your own worst enemy, and the only way to mitigate that threat is to embrace it. Act like your own worst enemy. Break your UI. Break your code. Do terrible things to your software.

Continue reading “Let Testers Do Terrible Things to Your Code”