User Acceptance Testing (UAT)

Understanding User Acceptance Testing (UAT)

User Acceptance Testing (UAT) is an essential step in the process of completing a project by the Hannon Hill Services Team. Team projects generally involve a variety of use cases to generate a QuickStart, implement a Module, or handle specific website-related requests. All such projects require testing of the functionality to determine if it performs as desired.

While the HH Services team performs thorough testing before handing off a project to a client, it is essential that you, the client, also test the performance of the code. This benefits you in two key ways:

1. You gain firsthand experience with how things work in Cascade.
2. You ensure that the implementation is delivered as agreed upon in the Statement of Work.

UAT Time Frame and Scope Considerations

Each project has a specified time frame for UAT, and all items must be submitted within that time frame. Any issues submitted outside of UAT are considered out of scope and will require a block of hours to complete.

To avoid additional costs or delays, we highly recommend taking full advantage of your UAT period. Failure to test can result in unnecessary delays in utilizing the work completed by the Services team. Be sure to allocate enough time for testing!

How to Conduct UAT Testing

Many clients are unsure about how best to conduct UAT. Common questions include:

• How is it done?
• What should you be looking for?
• How much work is involved?

The answers to these questions will differ from project to project, but some general best practices apply. For the purpose of this article, we’ll assume we are implementing a QuickStart.

Testing Your QuickStart Implementation

Regardless of whether your QuickStart involves a website redesign, you likely have requested that we build a set of page types, each with one or more components. Your request may also involve various block types. Every page, component, and block must be tested. It can be a lot of work! So how can you do it efficiently and systematically?

Prioritizing Page Types for Testing

It may seem counterintuitive, but often it is best to start with the page type that is likely to be most used, even if it is the most complex. Since other page types often use the same components with minor variations, testing the primary page type can help identify the majority of issues, reducing time spent on secondary pages. (Home pages can be an exception.)

Step-by-Step Testing Approach

1. Create and Save a Basic Page – Start with a page that includes the minimum number of required fields.
2. Use the “Show Edit Preview” Feature – This allows you to make changes and immediately view the impact.
3. Test Dedicated Components First – Focus on static elements like banners, carousels, and introductory text.
4. Test Selectable Components Next – Test dropdowns that allow selection among a set of components. Ensure each option is tested.

What to Look for During Testing

As you fill out each component, pay close attention to:

• Component Display – Does the component appear as expected?
• Code Visibility – Before entering any data, ensure no raw code is displayed on the page.
• Styling Accuracy – Compare fonts, sizes, and layouts against the provided designs.
• Text Behavior – Test with both small and large amounts of text to ensure proper layout adaptation.
• Layout Flexibility – If a text field is left blank, does the page adjust appropriately?
• Unexpected Inputs – Enter special characters or numbers where text is expected and vice versa.
• Color Accuracy – Ensure all colors match the design specifications.
• Image Behavior – Test with small and large images to check if they break the layout. Verify that images are properly centered and that the page still looks good if an image is not selected.

Verifying Layout and Component Interactions

Because “Show Edit Preview” can alter layouts due to the shared view with the form editor, always double-check by switching to “Preview Draft” or a saved version of the page.

• Move components up and down using the arrows to test spacing and prevent overlap.
• Test the minimum and maximum number of allowed components.
• Ensure layout consistency across different breakpoints.

Testing Input Fields for Usability

While testing, assess the usability of input fields for content providers:

• Are labels clear and understandable?
• Would help text improve usability?
• For specialized inputs (e.g., YouTube videos, Font Awesome icons), is it clear what information is required?
• Are links available to view icon choices, rather than just dropdown text?

Testing Blocks and Block Choosers

Some pages and components use block choosers for content selection. Ensure that:

• The chooser field or help text clearly indicates the correct block type to use.
• Using the wrong block type does not break the page.
• Blocks display correctly when used on relevant pages.
• Missing or improperly assigned blocks do not disrupt the layout.

Testing with Real Content

Another great way to test is by entering realistic content. Pretend you are building an actual page and confirm that all necessary options are available. While we don’t recommend adding all real content at the start of testing, using relevant content instead of generic placeholder text (e.g., Lorem Ipsum) can provide better insights.

UAT Ticket Response and Issue Resolution

Our developers will respond to all UAT tickets within two business days. However, some submitted issues may fall outside the project scope or differ from the Statement of Work. In such cases, our team will:

• Inform you why the issue is out of scope.
• Provide an estimate for any additional work if applicable.

The Importance of Thorough UAT

User Acceptance Testing requires patience and attention to detail. Allocating sufficient time ensures testing is completed within the allotted period.

A well-executed UAT process ultimately:

• Saves time and money.
• Helps you learn how to use the features you’ve requested.
• Ensures your project is delivered as expected.

By following these best practices, you can maximize the benefits of UAT and ensure a successful project launch!