<% 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 Program Track Completed Content Track Completed Pages Track Completed Page Builder 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 Knowledge Assistant Track Completed Multi-Language Experiences Track Completed Fall '22 Release Highlights Track Completed Spring '23 Release Highlights Track Completed Chat Track Completed Summer '23 Release Highlights Track Completed Fall '23 Release Highlights 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
Upgrade Theme for Search Frontend Experiences
Arrow Back
Completed
Introduction
Introduction
completed
Completed 1
Step 1
Create a Branch
completed
Completed 2
Step 2
Pre-Work for Theme Upgrade
completed
Completed 3
Step 3
Upgrade the Theme
completed
Completed 4
Step 4
Process Version Updates
completed
Completed 5
Step 5
QA Your Search Site
completed
Completed 6
Step 6
Push to Production
completed
Completed 7
Step 7
Common Upgrade Issues
completed
Completed 8
Step 8
Patches - Apply a Diff
completed
Completed 9
Step 9
Rebuild Your Site
completed
home

Step 5: QA Your Search Site

Now that you’ve actually upgraded the theme, it’s time to check that everything looks and works as expected. This is a great opportunity to make sure all changes you made are good and that you’ve reconciled everything you need to.

Test Live Preview Thoroughly

Follow the steps outlined in the Debug and QA module. Since your changes were only on the frontend, you can skip the search quality QA and focus primarily on browser and feature QA, as well as user interface QA. Some common things to check for are:

  • Run through queries that surface results for each vertical and compare side by side with your staging or production link. Make sure to check a) all verticals searches and universal search, and b) both mobile & desktop views.
  • If you added any custom CSS, it’s possible there may be some impact to your styling after upgrading your theme as HTML class names or structures may have changed.
  • Any other custom work added to the experience.
  • If there are any visual theme upgrade changes that are automatically applied to all experiences, make sure you see the changes in your experience.
    • For example, Theme v1.25 fixed a styling regression where the variable --yxt-color-text-primary did not change the paragraph font color on cards. Once you upgrade, check that the paragraph font color is using this variable.

Note: You might be wondering why you need to go through such a thorough QA process again. It’s important to recognize that sometimes upgrades may also include breaking changes or regressions. Our Product team will make note of any breaking changes or regressions that they’re aware of in the release post. Take a look at the Theme version 1.29 to see an example of what this might look like! However, it’s critical that you thoroughly QA your experience to confirm that it’s functioning as you’d expect and that there are no regressions or breaking changes that the Yext team is unaware of.

Commit Changes Once Live Preview Looks Good

Make sure to add a commit tag. Monitor the deploy on the Deploys screen to make sure it goes through successfully.

Code Editor Commit Changes popup with commit message and tag filled in

Feedback
<% elem.innerText %>