What is Augmented Reality and How to Test It?

The narrow use of extended reality, primarily centered on entertainment, has expanded its limits. Today, it offers endless possibilities for education, training, e-commerce, engineering, and many more.

Still, nowadays, not that many companies are prepared to implement this technology yet. But the active development of Web 3.0 and Metaverse demonstrate that XR integration is inevitable. Thus, QA engineers should learn how to work with innovative solutions for any niche.

What Is AR?

Augmented reality is a great starting point for businesses. Because XR is relatively new to both enterprises and users, AR provides a simpler solution to customer demands. However, there is nothing simple about testing AR. But with practice and some insights, it will become easier.

First, let’s start by clearly defending AR and separating it from other realities.

• XR – extended reality. An umbrella term that encompasses all related technologies.
• AR – augmented reality. It uses your real-world, live environment and overlays digital content on top. A good example is AccuVein. It reads patients’ heat signatures to detect vein patterns. By displaying the image on a patient’s skin, medical practitioners can easily locate needed vessels.
• MR – mixed reality. It merges actual and virtual realities to create a setting in which you can interact with both. For instance, take Windows’ HoloLens, add a pair of haptic gloves, and you got yourself in the MR world. The main distinction between AR and MR is that you cannot physically, or metaphysically, interact with AR content.
• VR – virtual reality. It submerges a user into a virtual world by using wearable devices. Most of you are familiar with Oculus Rift. A headset, headphones, and controllers create an immersive experience within an environment where you can do just about anything.

So, in simple words, augmented reality is the combination of a physical setting and virtual information generated as an added layer.

How AR Works?

To better understand what awaits QA engineers testing AR apps, it is important to know how such software works. Almost any AR app embraces 4 core principles:

#1. Capturing the environment

This involves scanning the live setting via a camera-equipped device. So, the app needs to ‘navigate’ the scene it should work in. Think IKEA Place. It uses this particular function to view users’ apartments and add selected objects on top.

#2. Identifying the anchor point

In order to show virtual content, the app needs to find the subject/place upon which to overlay it. For instance, Instagram filters are able to precisely recognize a human face and display images on needed features. And thanks to that anchor, you can move around, and the filter will follow.

#3. Retrieving correct data

Because AR apps are used in 3D environments, they should demonstrate accurate images in real-time. Take Machine A’s virtual store. As the user ‘steps into’ the space, the app constantly updates its visuals to display a corresponding section.

#4. Consistently linking reality and AR

To not ruin the immersion, there should be a continuous connection between the two worlds. Even when the user explores the app in various conditions for a prolonged period. For example, Pull & Bear’s Pacific Game is intended for lengthy engagement, thus, must function steadily.

What Are Common Issues with AR Testing?

Best practices for AR software testing services are still work-in-progress. So, for now, the best approach is trial and error. Hence, AR introduces a few specific challenges you should be prepared for.

The 3D Aspect of AR

AR relies on both creativity and the real world. With this comes the most prominent difficulty with AR app testing – the near-infinite number of environments. Ensuring correct data projection for different surfaces, structures, objects, lighting, etc., and the three-dimensional view can get time-consuming.

Space Mapping in Motion

What makes an AR app practical or fun is its live tracking. Location, motion, movement direction, and device rotation must be interpreted appropriately at all times. AR software can use infrared light, sensors, or GPS data to assure defect-free superimposition. But even with these, fast transitions can become a challenge.

Device Variability

The amplified usage of AR translates to an increase in implementation options. OSs, screen resolutions, camera capabilities, etc., are still to be checked. But the shift from mobile hardware to smart glasses, kiosk systems, installations, etc. makes AR technology testing quite demanding. For this, emulators and cloud devices can be of great assistance. Yet they offer rather limited experience when it comes to AR.

What Are the Usual Testing Types for AR?

To test augmented reality applications, you should be prepared for extra effort. But even with the peculiarities of AR testing, there are some traditional aspects to it.

• Functional testing – verifying whether every software feature operates as intended. Checking main app functions is crucial. But with AR, this testing may take an approach distinct from its ‘classic’ variant. You will begin with logins and menu displays. And eventually move onto assessing virtual content placement, space/object recognition, and so on.
• Compatibility testing – examining app performance under various software/hardware conditions. Because AR can be used in so many ways, ensuring optimal usage in diverse configurations is an important step towards a quality app. If there is a target audience that uses specific setups, it is essential to customize the AR app to their needs.
• Accessibility testing – assuring usability for as many individuals as possible. AR can be an enriching and valuable experience. In order to secure positive UX, making an app accessible to all is necessary. For instance, color and contrast selection can be of great value to people with visual disabilities. Adjusting control options to fit the needs of those with limited mobility will make a big difference too.
• Compliance testing – making sure the app conforms to particular regulations. Customer data protection is paramount for any respectable app. Because AR software uses real-time physical data, safeguarding any recorded information is a must. You should also keep safety guidelines in mind. Imagine an AR obstacle course for firefighters’ training. If an image is displayed incorrectly or obscures the authentic view, physical damage is a possibility.
• UI testing – ensuring consistency and integrity of the app’s visual layer. AR software may be a bit confusing for some users (most of them at first, in fact). Because consumers have to interact with the app and the world at the same time, the UI needs to be extremely user-friendly. Not losing focus and effortlessly operating the program is a priority.
• Integration testing – checking multiple software features’ combined functioning. Particularly important for AR apps is the constant joint workflow between the device’s camera and other components. For example, if the application opens and displays its features but cannot anchor on the intended object, this renders the software futile.

What to Pay Attention to during AR Testing?

You should consider a few unique aspects when providing QA services for an AR app.

Safe Utilization

Regardless of the space an AR app is used in, an empty room, a furnished apartment, public space, safety should take precedence. As a QA engineer, you should study how an app behaves in different weather, lighting, and locations. So, to protect your users, engage your creative side and think of as many use scenarios as possible.

Motion Sickness

Also called cybersickness, it is quite common among XR users. Frontiers reports that up to 95% of consumers experience it in some form (from headaches to emesis). Users may ignore minor symptoms. In such a case, prolonged AR usage can lead to more serious issues. For instance, initial eyestrain, common with AR, can develop into myopia. Thus, it is sensible to test the safety mechanisms present within the app. It can be occasional notifications (a reminder to rest) or extended experience optimizations (change of scenery, color adjustments, etc.).

Battery Life

AR apps are rather demanding when it comes to battery use. But you do not want users sticking to a wall with an outlet. Noting how an app works on low charge, whether it runs not-currently-in-use functions in the background, or monitors CPU state can help identify solutions to the issue (as per ARCore). Options for performance improvement should be customized and provided to users in a timely and non-invasive manner.

How to Test Augmented Reality Applications?

Currently, there is no standardization for AR testing. But there is a framework that can be useful. Let’s go over it step by step.

1. Study Software Requirements

It is where every testing starts. If you do not know your app, there is no proper way to test it. The more familiar you are with the software, the more you will be able to do for it as a QA engineer. Learn the app’s functionality and goals. This will be essential for creating use/test cases.

2. Research Your Audience

This may be a bit of a non-standard step, but it will come in handy during testing. For example, if you are working on an AR training app for pilots, if there is a mislabeled/misrepresented component, this can become an issue. Best-case scenario – users will point out the flaw, which would compromise their trust. Worst-case scenario, their education will be negatively impacted.

3. Set Up the Working Environment

Preparing devices and spaces needed for testing will help you immerse yourself into the intended consumers’ world. By stepping into the shoes of potential users, you will be able to better understand their needs and usage options.

4. Define Test Coverage

You should clearly understand what to test. Environment scanning, object registration/tracking, data appropriateness, input variety, etc. Determining your initial focus area will help you think through potential test scenarios and devise suitable test suits.

5. Establish Needed Tests

When deciding what testing to perform, you need to consider the project mission (in case there is no document outlining this). For instance, you might not need to run compliance testing when working on an app similar to Snapchat City Filter. While the opposite would be true for something like AR-throscopy (arthroscopy simulator for med students). So, prioritize your tasks and do not try to do everything at once.

6. Collaborate with the Team

Most likely, you will not be the only one new to AR. Partnering up with other members, whether from QA or dev teams, can help you learn faster. And by consulting with more skilled experts, you can gain first-hand insights into the essentials of AR app testing.

7. Innovate

There is no golden rule for AR testing. Currently, the top solution is ‘mess around and find out’. After all, there is no better way to test an AR app than actually using it. And with a little bit of creativity, you will be able to predict user thinking and behavior. Thus, writing better test cases and, ultimately, enhancing the app’s quality.

To Sum Up

It may be a bit overwhelming when first trying AR testing. But it is true for any novel undertaking. Remember, doing your best is the best anybody can do. And as a QA engineer, your goal is to help produce an app with no critical defects. The rest will sort itself out.

Good luck, and keep learning.