How to conduct a mobile usability test?

It is important to know that there are more variables when it comes to recording mobile usability test. The technical set-up for this test is quite simple, but it is a little bit different from the standard usability testing.

In this article, we are going to look at how to set up and conduct a mobile user test.

First, what is mobile usability testing?

This is a usability testing of a website, application, accessory, or anything else that a user might interact with on a mobile platform, such as a smartphone or tablet.

When and why should you conduct a mobile usability test?

Anybody that regularly conducts this type of test would tell you how powerful it can be.

Seeing is believing; a twenty minutes video clip showing users how to use your software is more powerful and eloquent than you can say. As with any usability study, increasing the ease of use leads to increased revenue and happier customers.

The earlier the testing is done, the better. This type of test can quickly find and correct major problems that might be extremely difficult or costly to fix in a finished product. So, user testing, without a doubt, is the best way of gathering requirements.

Setting Up and Conducting a Mobile Usability Test

It is important to know that any of these guidelines can be adapted to fit a specific need or desire, even if you are not using a mobile lab at all.However, without a mobile lab, it’s more difficult to observe and capture users’ interactions with your mobile site or app.

setting up mobile test lab with camera

A simple mobile usability lab only requires three things:

  • A camera (i.e. a webcam) with some extendable or cradle to observe and capture the mobile device and user’s interactions.
  • A computer to display the camera field for observers.
  • A recording software to record the session for later review and analysis.

Ok, what should a standard mobile user lab look like?

Here’s what a standard mobile lab should look like:

Use two webcams 

One should be on an extendable arm positioned to record the device from above, and the other to see the user’s face.

As long as the webcam shows their face, you will be able to get a good picture of where they are in the experience.

It also allows you to observe the user’s gestures interaction. This way, you can tell if they try to tap, swipe, pinch, or otherwise interact in ways that are not supported.

The webcam focused on their faces, allows you to see their emotional response throughout the test.This valuable feedback allows for real-time, user-specific lines of questioning based on their reactions.

Depending on the objectives of the test and the platform being used, you can occasionally take advantage of platform-specific features such iOS’s Airplay, Mirroring to show the device’s screen on the computer.

Tools You Can Use

usability testing tools available in the market

Morae:

You can use Techsmith’s Morae suite to capture and record the webcam video and audio feeds.This way, you can see what the users are doing while they are doing it and record this for post-test analysis. It also allows you to observe the user’s experience from another location remotely. They can focus on task at hand, rather than turning to talk to a moderator. Finally, Morae offers unique post-test analysis capabilities, including storyboard editing to make video clips of the test highlights.

Userzoom

Ok, apart from Morae, you can also use Userzoom. This tool consists of testing large samples and allows you to build your study and task. It creates a study with task for users to perform in their natural environment. Also, Userzoom can test any mobile website or a hosted prototype on both iOS and Android services. With this tool, you are sure of getting quality data.

Silverback

This is another great tool you can use to do your testing. It has similar functions with that of Userzoom. It captures the face and also gets to see what the user is doing clearly. Silverback enables the recording, editing, analysis and playback of testing sessions. You can easily share the video stream with anyone who wants to view the session remotely. We have found that video clips are an excellent way of illustrating our findings for our clients and their project managers.

Irrespective of the tools, you would need to define your goals both business and test goals to get insights and ask the right questions to your subjects.

Outsourcing QA | A Doomsday prepper’s guide to an apocalypse-ready webapp

You might be familiar with Murphy’s law which says ‘Anything that can go wrong, will go wrong’. Software isn’t immune to that. But that’s often the last of your worries because the plate’s always full!

Well, not anymore!

Prepping your webapp via a professional third party QA vendor

QA is like checking your life jacket before diving. There are professionals that run quality tests to eliminate the possibilities of a malfunction.

Delegating QA to a professional third party is not a bad idea. If you’re thinking of adding or improving a QA process in your existing SDLC, then there are two ways of doing that. One is to go with an inexperienced local team and another option is to outsource professionals.

An experienced QA engineer is aware of all the possible errors and prepares test cases accordingly.

It’s not safe out there and you must be on-guard at all times.

The right & only way to outsource QA or any help for that matter

Clear communication.

It is vital for coordination. While hunting, Preppers require patience and coordination to hunt. Their coordination through communication determines if they’ll eat or sleep hungry.

You need to think of outsourcing as co-operative hunting. Communication is the key.

50% of the problems are instantly solved with an active and fitting communication channel. That’s the only way both the parties would know what’s expected of them. Fluent and relevant dialogues can lead to result-driven partnerships.

Start by talking about these aspects:

  • Project requirements
  • Defects in software products during all stages of the development process
  • Product quality evaluation
  • Product’s usability

Delegation gets more done.

Don’t “Alpha to Charlie, we need cover!” your vendor. Just plain communication would do

An elaborate plan is one common thing in every prepper’s guide. The plan is made keeping every possible worst case scenario in mind.

Your engagement model is that plan.

Start by defining the type of outsourcing your project requires. Incremental outsourcing allows you to mitigate your risks by dividing work into smaller, more manageable projects. Total outsourcing involves outsourcing multiple projects and programs to a service provider.

Beware of these fatal threats. It might kill your webapp

Pokeberries might look tempting and edible but they’re poisonous.

A webapp is like the wild. There are things that look friendly and consumable but are not. Here’s a handy list of common things that are used to steal user data and are poisonous for your webapp.

1. Cross site scripting (XSS)

Hackers can use malicious scripts across the site to redirect your users to other phishing sites. Via these phishing sites they can extract customer’s information and exploit their machines.

2. Cross site request forgery

Using cross site request forgery hackers can link their malicious website on your webapp. These links when clicked on, compromises user credentials and other personal information.

3. Code injections

Code injections are rather common, they are used to alter the functioning of a webapp and make it crash.

4. Server side includes (SSI) injections

Server side injections are like code injections but more severe. As the name suggests it’s injected on server side.

5. Authorization bypass

Authorization for webapps acts like biometric access control. A successful bypass means the breach of protected information, which can lead to misuse of website data.

Not roughing up your webapp can lead to:

  • Terrible speed
  • Subpar performance
  • Compromised UX
  • High bounce rate
  • Reduced search engine ranks
  • Payment interface issues
  • Loss of potential customers & sales

Testing before sending it out there in the wilderness

Browser Compatibility Testing

Test the traps with something (exclude yourself) after deploying. QA reduces the risks of failure.

Different browsers render websites differently. Bug fixes and critical changes make it more difficult to find a sweet spot for compatibility. QA engineers test all the platforms that your website will run on.

Testing on multiple devices is essential because people use mobiles devices more than computers. Compatibility issues lead to poor performance and it can decrease traffic and affect conversion.

Performance and user experience is one of those things that will instantly affect your business.

With comprehensive compatibility tests you can prevent loss of potential customers & sales. Better loading speeds and lower bounce rates aid in better SEO ranks too.

UX Testing

See the world with a survivor’s eyes and walk in their shoes. That’s how you come up with unusual solutions.

UX testing is seeing your webapp with your user’s eye. With test case scenarios you’re taking a walk in their shoes.

Use real time user-behaviour data to improve user flows and fix abnormalities within the webapp. With the help of UX testing you can determine if your design, user flow, and copy are working as intended.

Functional Testing

Functional testing surfaces friction in your webapp, if any. It also reveals crucial issues of your website’s functionality like UI problems and substandard user experience.

Using functional test case scenarios, QA engineers can compare the functionality of your website against the defined scope.

Load & Performance Testing

This testing uses staging servers to determine maximum load & performance. It’ll help you figure out if you have delayed server responses, crashes, and other potential problems.

Load and performance tests are designed around your business requirements, server configuration, historical traffic on your website, anticipated future traffic of your website.

JMeter and Loadrunner are used to simulate traffic to test your website. These tests help QA engineers to identify key performance indicators for your webapp and server.

Security Testing

You can manually get rid of bugs and faults but new ones keep appearing hence the automated tests for passive safety.

QA engineers use a mix of manual and automated testing techniques on your staging servers to identify security vulnerabilities on your website.

Test Automation

Selenium does the bug hunting for your webapp. It uses test scripts to mimic the user interface over and over. You don’t have to live test manually every time there’s a small change.

Although not all aspects of website could run using automated testing, even if some vital checkpoints are automated, it saves manpower cost to a huge extent.

QA can protect your webapp and cut costs at same time

Your website’s content assets and customer information are key drivers for your success. Security vulnerabilities can cause loss of data, customers, and reputation. A QA team can save your webapp, customers, and sales. Wise men say

“Better safe than sorry”

QA can reduce 30-40% costs of maintaining the quality of the webapp.

We’re no Doomsday preppers but we do have a team of QA/QC engineers that leave no margin for errors and makes your webapp apocalypse-ready.

Say hi, we can make your product fit enough to survive.