<% user.full_name %>
<% util.level ? util.level.title : '' %>
Explorer Pioneer Apollo Viking Voyager Pathfinder Orion
Points
<% user.points ? user.points.toLocaleString() : 0 %>
Badges
<% util.badgeCount %>
Streaks
Congratulations You've <% util.newestBadge.isCurriculum ? 'completed' : 'earned' %> the
<% util.newestBadge.title %> <% util.newestBadge.isCurriculum ? 'curriculum' : 'badge' %>!
previous
next
Share to Social Media
Linked In Facebook
Status
<% util.level ? util.level.title : '' %>
<% util.level ? util.level.points : '' %>
<% util.nextLevel ? util.nextLevel.title : '' %>
<% util.nextLevel ? util.nextLevel.points : '' %>
Level up! <% util.levelPointsRemaining %> points to go
Level up! <% util.levelPointsRemaining %> points to go
Badges
Completed Hitchhikers Track Completed Knowledge Graph Track Completed Pages Track Completed Search Backend Track Completed Search Frontend Theme Track Completed Search UI React Track Completed Solution Templates and the Admin Console Track Completed Technical Skills Track Completed Platform Basics Track Completed Listings Track Completed Reviews Track Completed Industry Overview Track Completed Analytics Track Completed Industry Overview & Product Basics Track Completed Multi-Language Experiences Track Completed Chat Track
<% util.expandBadges ? 'Less' : 'More' %>
Playground Accounts
New +
No Playground Accounts
Create Playground +
View Profile
Log Out loading
Mission Complete! 🚀
Congratulations, you’ve completed your first module!

We hope you enjoy exploring the rest of the site. Please don’t forget to leave us feedback - we are constantly looking to improve. Happy Hitchhiking!
Home
Welcome to Hitchhikers! 👋
To learn more about the platform we encourage you to get started by completing the Hitchhikers Program Track and earning your first badge!
Start Here
Close notification
Guide
Get Started with Page Builder
Arrow Back
Completed
Introduction
Introduction
completed
Completed 1
Step 1
Set Up Content
completed
Completed 2
Step 2
Create a Site
completed
Completed 3
Step 3
Customize Content
completed
Completed 4
Step 4
Match Your Brand's Styling
completed
Completed 5
Step 5
Update Page Settings
completed
Completed 6
Step 6
QA
completed
Completed 7
Step 7
Launch and Integrate
completed
Completed 8
Step 8
Post-Launch Analytics
completed
home

Step 6: QA

Before we push the pages live, we’ll want to run a few quick checks on the page. As a reminder, Yext Page Builder pages are designed for a quick launch, meaning that out of the box, the page template will be mobile- and tablet-optimized, tested across various browsers, and engineered for SEO success. However, you should still test various breakpoints and devices to ensure success.

QA is extremely important. Pages with issues like slow load times, typos, or broken links lead to a poor customer experience, higher bounce rates, and fewer conversions. Doing QA helps eliminate those issues and ensure that once pages are published they are ready to be seen by consumers, and are optimized for the best customer experience.

QA Process

There are two parts to the QA process:

  1. Complete thorough internal testing prior to sending a staging link to any other stakeholders for QA. We will cover what to look for in your QA below.
  2. Once you’ve QA’d your page template yourself, it’s helpful to get feedback from others. You can share the Preview URL to have other stakeholders review the page template.

When QAing Pages it is important to keep track of your QA items in a structured way to have a clear understanding of what you have tested. Then you can create a list of what the issues are, including the priority, and can systematically take steps to resolve them. Some issues that arise may prevent you from launching pages, whereas some issues may be more aesthetic or stylistic and can be resolved after the launch process. Regardless of what comes up, you want to make sure you have a process in place so you can effectively work through items in their order of priority.

Types of QA

You want to make sure that everything appears and functions correctly, from load time and browser testing, to data mapping and spell checks. Below is a list of the main categories QA items will fall under, and some of the items to look for in those categories.

Technical

  • Are the fields appearing properly based on the mappings?
  • Are there any broken links?
  • Are there any load time issues?
  • Are the pages rendered the same across browsers?
  • If you integrated with a third-party analytics provider, is the integration working as expected?

Visual

  • Are things properly aligned?
  • Does the design match your branding?
  • Are modules and content optimized for other device types (see below for more on device testing)?

Data

  • Are the fields mapped properly?
  • Are you missing any data?
  • Are the URLs all correct and pointing to the right environment?

Enhancement

  • Are there any new features you’re realizing you need/want?

Device Testing

Within the Page Builder interface, there are device selectors on the right side of the page preview. The left option is for desktop, the middle option is for tablet, and the third option is for mobile. Make sure to click on these various device options to ensure that the content and modules are optimized and aligned to your expectations. For example, you may want to shorten or lengthen the amount of text on a given field to help optimize the mobile layout. Maybe you decide you want to add additional styling on mobile screens with custom CSS; that is possible, too!

<% elem.innerText %>