Personalization Testing — Builder 1.0 & 2.0

1. Purpose & Scope

This article documents the Personalization testing protocol for the Tiled December 2025 release. Personalization allows content creators to define variable fields within tiles — text, image, video, and hotspot — that are dynamically populated per viewer or recipient at runtime. This release cycle validates personalization behavior across Builder 1.0 and 2.0, the Viewer, and Share Links.

Scope: All Tiled users with Builder access (Editor role and above). QA testers in Breakout Room 1. Applicable to Library Administrators configuring required personalization fields.

2. Testing Team — BR-1

3. Personalization Tile Types — Feature Reference

Personalization can be applied to the following tile types in both Builder 1.0 and 2.0. Each tile type must be tested independently as personalization behavior and field options differ per type.

4. Known Issue at Time of Testing

5. Testing Instructions

For each tile type listed in Section 3, complete the following steps in both Builder 1.0 and Builder 2.0:

1. Create a new microapp on the preprod environment.
2. Add a tile of each type (Text, Image, Video, Hotspot) to the microapp.
3. Enable personalization on each tile and configure a personalization field.
4. Set a default value for each personalized field.
5. Preview the microapp in Builder Preview and verify the personalized field renders with its default value.
6. Open the microapp in the Viewer and test the personalization experience — change field values and verify the tile content updates correctly.
7. Generate a Share Link and open it externally. Test personalization behavior in the shared view. Note: expect known rendering issues for personalized text in Share Links.
8. Log any unexpected behavior in the Issues Found table and file a Jira ticket.

6. Additional Personalization Scenarios to Explore

6.1 Image Tile — URL as Default Source

When setting a URL as the default image source for a personalized Image tile:

•   Verify that entering an invalid or incomplete URL does not enable the Save button.
•   Verify that only a fully valid, resolvable image URL enables Save.
•   Verify the image renders correctly from the URL in Preview, Viewer, and Share Link.

6.2 Multi-Target Hotspot Tiles

Multi-target (multi-hotspot) tiles have a minimum height constraint in the Builder. Validate the following:

•   In the Builder, the hotspot tile may appear taller than its configured tile boundary — this is a known visual discrepancy in the Builder only.
•   In Preview and Viewer, the hotspot tile must respect its configured tile dimensions exactly.
•   Verify click targets within the multi-hotspot tile are correct and functional in Viewer and Share Link.

6.3 Tile Visibility — Hide While Selected

When hiding a tile via the Layers panel:

•   The tile should remain selected on the canvas after being hidden.
•   The tile's properties should remain visible in the Properties panel while hidden.
•   Verify this behavior in both Builder 1.0 and 2.0.

6.4 Personalization Field Duplication Behavior

When duplicating a personalized tile (Shift+Cmd+D or copy/paste):

•   The duplicate tile retains its personalization field link. Renaming the field on the duplicate must be done by creating a new personalization field from the dropdown.
•   Verify that changing the personalization field on the duplicate does not affect the original tile.
•   Verify that creating a new personalization field on the duplicate does not result in format loss.

7. Open Feature Requests from This Testing Cycle

The following UX improvement requests were raised by testers during Breakout Room 1 and are pending triage. These are not defects — they are logged for product roadmap consideration.

8. Audit Evidence

•   Testing results recorded in the December 2025 QA Testing Matrix (KB-vDec25-05) constitute SOC 2 CC8.1 (Change Management) evidence for personalization feature validation.
•   All Jira tickets filed during this testing session constitute CC4.2 (Evaluation of Control Deficiencies) evidence for defect identification and remediation tracking.
•   Feature requests with no assigned Jira ticket are recorded in this article for traceability. They require a Jira ticket before entering the development backlog.

9. Change History