UAT Testing

A short orientation for UAT testers before they validate ClientVerse against the test plan. It covers just enough of the system to test confidently — plus the few specialty actions a tester needs to exercise.

Objectives

By the end you can: - Log in, navigate, and search the system. - Work any object the same way — search, open, read the layout, create, update. - Perform the specialty actions the test plan exercises (lists, campaigns, opportunities, relationships). - Follow the UAT test plan and the defect-logging process.

Prerequisites

A UAT login to the test/sandbox org, and the UAT test plan.

Agenda

1. Logging in to the test org.
2. Navigating — the home dashboard, the navigation bar, the global search bar.
3. Using global search to find any record fast.
4. Working with objects (Contacts as the example) — object searching, opening a record, reading the layout (dashboard / tabs / details vs. associated data), creating a record, updating a record. Every object works the same way; only the data points differ.
5. Special topics for testers:
6. Where to find relationship intelligence (ERM relationships).
7. Create a list and add to it.
8. Associate a list to a campaign and activate the campaign.
9. Move an opportunity through its stages and close it.
10. The UAT test plan & process — how to execute test cases and log defects (use the Support Ticket button; capture a description + screenshot).

Hands-on (during/after)

Run two assigned test cases end-to-end: one create/update on an object, one multi-step flow (list → campaign, or opportunity stage change → close). Log any issue with a clear description and screenshot.

You're ready when…

You can execute a test case independently, tell a real defect from expected behavior, and log it so engineering can reproduce it.

Related

• ClientVerse Introduction — the fuller navigation/searching basics.
• ../../uat/CLAUDE.md — the UAT test plans these testers execute.