The Extended Reality Blueprint

13Quality

QUALITY ASSURANCE, OR QA, testing is a tedious but necessary part of producing any technical product. Where you tested for usability and experiential feedback earlier in the process, you will now test for technical or functional issues with the extended reality experience. Some organizations have a dedicated QA resource or team, and other smaller teams must lean on each other to perform this type of testing in addition to their primary role. Regardless of who is testing, ensure that it's someone who was not directly responsible for developing the sections of the project that they are testing. Each component should require a second, if not third, set of eyes before passing this review process. QA testing will likely go through multiple rounds of testing, especially if you're leveraging new and untested features and functionality.

Bugs

Bugs are the most common thing you'll find during your testing phase. They present themselves as a fault or error in the experience that testers encounter while attempting to complete the playable loop or use accompanying features. Any issue you encounter when testing the experience is likely classified as a bug, and as you document these, make sure to gather as many details as you can to help the developers pinpoint the issue and brainstorm a solution. Some bugs can be funny. One time we had a canister in an experience that continued to infinitely replicate itself as soon as it was opened. After about 10 seconds, the ground was covered ...