Run UAT

How to run user acceptance testing for an implementation, record which scenarios you've passed, and raise issues against the ones that don't.

How UAT works

UAT in the Project Tracker is ongoing — there are no rounds, cycles, or sign-off. The UAT tab holds a list of test scenarios FullClarity has prepared for your engagement, and each tester ticks off the scenarios they've personally run and confirmed work. As fixes are made and you re-test, you keep ticking; as you find problems, you raise issues against the scenario. The view simply reflects the current state of testing at any moment.

The point of UAT is the same as ever: your own users walk through their own real workflow and confirm the system behaves correctly for them before go-live.

Who runs the tests

UAT is run by people on your side — the customer team — not by FullClarity. FullClarity provides the scenarios, but the value of UAT comes from your own users exercising the system.

Common arrangements:

  • A single nominated tester runs every scenario themselves.
  • Each scenario is run by whoever owns that area of the business (the AP scenarios go to the AP person, the project setup scenarios go to a project administrator).
  • A mix — one person runs the core path, subject-matter experts run their specialist scenarios.

Because each tester has their own pass column (see below), more than one person can take part and you can see at a glance who has passed what.

The test scenarios

Each row on the UAT tab is a test scenario set up by FullClarity for your engagement. The relevant columns:

  • Test code — a short identifier (sometimes blank if FullClarity hasn't assigned codes yet).
  • Title — what the scenario tests (for example, Create a progress claim on a stage-billed contract).
  • Scenario — a paragraph describing the business situation being tested.
  • Steps — the numbered steps the tester follows in NetSuite.
  • Expected result — what the tester should see when they complete the steps.
  • Pass/Fail — a read-only rollup showing whether the scenario has passed overall (see Recording UAT results).
  • A pass checkbox per tester — one tick-box column for each person taking part in UAT. Your own column is shown first and is the only one you can tick; everyone else's is visible but read-only to you.
  • 🚩 (raise issue) — a flag you click to raise an issue against the scenario when it doesn't behave as expected.

If your scenarios look sparse or generic, ask your FullClarity consultant — they can refine or add scenarios at any time.

Recording a pass

  1. Pick a row to test. Read its Scenario, Steps, and Expected result.
  2. Do the steps in NetSuite.
  3. Compare what happened against the Expected result.
  4. If it behaved exactly as the Expected result described, tick your own pass checkbox on that row.

That's it — ticking your pass column means "I ran this scenario and it behaved as expected." The tick saves automatically, and the next time anyone opens the tracker they'll see it in your column.

Leaving a checkbox un-ticked simply means you haven't passed that scenario yet — whether because you haven't run it, or because it didn't behave correctly. There's no separate "untested", "blocked", or "fail" value to set on the row; if a scenario doesn't behave as expected, you raise an issue against it (below).

Each tester ticks independently, so you can see who has confirmed each scenario. For how the columns interact and what makes the Pass/Fail rollup turn green, see Recording UAT results.

When a test fails — raise an issue from the flag

When a scenario doesn't behave as the Expected result described, click the 🚩 flag in the raise-issue column on that row. The New Issue form opens, pre-filled with:

  • A Title like UAT fail: <test code> — <scenario title>, so the issue and the test are obviously linked.
  • A link back to the test scenario, so FullClarity can find it in seconds.

You complete the rest:

  1. Add a Description — what you actually saw versus what was expected.
  2. Optionally use First note to add a longer narrative and attach screenshots — paste them straight from the clipboard (Cmd+Shift+4 → Cmd+V on Mac, Snipping Tool → Ctrl+V on Windows). See Add notes to an issue for the full attachment surface.
  3. Set a Priority (defaults to Medium).
  4. Adjust the Title if the auto-generated one isn't quite right.
  5. Click Create.

The issue lands on the Issues tab with the next available issue number and stays linked to the scenario. The scenario's row shows the linked issue (for example, as a flag icon with the issue number, ⚑ #3). A single scenario can carry more than one linked issue — they appear together (for example, ⚑ #3 #4) if you raise several against the same test.

If you'd rather not log an issue right now (maybe you want to gather more information first), click Cancel on the form — nothing is recorded against the scenario.

While a scenario has an open linked issue, its Pass/Fail rollup stays un-ticked, even if a tester has ticked their pass column. The rollup only turns to pass once the issue is resolved and you've accepted the fix — see below.

Working through the scenarios

The order you work scenarios in is up to you. A few common patterns:

  • Top-to-bottom — simplest and predictable.
  • By area — group scenarios for the same NetSuite area together (all the AR scenarios, then all the AP scenarios), so you stay in one part of the system at a time.
  • Critical first — run the must-pass scenarios early so you know whether the implementation has go-live-blocking issues before spending time on edge cases.

As fixes land, re-run the affected scenarios and tick your pass column once they behave correctly.

When FullClarity fixes a linked issue — accept or reopen

When FullClarity marks a linked issue as Done, that does not immediately clear it from the UAT view. The issue stays visible on the scenario's row as a link — shown in green to indicate FullClarity considers it fixed — and keeps the Pass/Fail rollup un-ticked until you confirm the fix.

To confirm or reject the fix, click the issue link on the UAT tab (or open the issue's notes from the Notes cell on the Issues tab). On the issue's notes panel you'll find:

  • Accept — you've confirmed the fix is good. The issue stops blocking the scenario's rollup, so the scenario can now roll up to a pass (provided a tester has ticked their pass column). The issue stays Done.
  • Reopen — the fix didn't work. The issue goes back to Open and again blocks the rollup until it's fixed and accepted.

This keeps the customer in control of when a scenario is truly considered passed — a fix isn't "done" for UAT purposes until you've accepted it.

Working in parallel

More than one person can record results at the same time. The tracker keeps everyone's view in sync — when you tick a pass or raise an issue, others see it on their next refresh. If two people happen to change the same thing at once, the most recent change wins and a notification appears so both people know what happened.

Last Updated: