---
title: "Do a Quick Test"
description: "Run an object's logic on a single record for instant feedback while you iterate."
---

<div style="padding: 14px 16px; border: 0.5px solid var(--corridor-purple-border); border-radius: 12px; background: var(--corridor-purple-soft); margin-bottom: 1.5rem;">
  <div style="display: flex; align-items: center; gap: 7px; margin-bottom: 8px;">
    <svg width="16" height="16" viewBox="0 0 16 16" fill="none">
      <path d="M9 2L4 9h4l-1 5 5-7H8l1-5z" stroke="var(--corridor-purple)" stroke-width="1.2" stroke-linecap="round" stroke-linejoin="round"/>
    </svg>
    <span style="font-size: 11px; font-weight: 500; letter-spacing: 0.05em; text-transform: uppercase; color: var(--corridor-purple);">TL;DR</span>
  </div>
  <div style="font-size: 13px; color: var(--sl-color-white); line-height: 1.65;">
    A <strong>Quick Test</strong> runs an aggregated <strong>Data Element</strong> on one record and shows the result right away, no full simulation needed. Enter a record <code>id</code> on the <strong>Quick Test</strong> tab to check your aggregation while you build it.
  </div>
</div>

## What is it?

Quick Test runs on an [aggregated Data Element](/user-guide/how-tos/register-a-data-aggregate/), a Data Element with **Is Aggregated** turned on. You point it at one record, tweak the logic, and re-run until it's right, all on the same tab.

It's the fast counterpart to a full [Simulation](/user-guide/how-tos/run-a-simulation/), use it while developing, then run a Simulation to validate.

<table class="de-compare">
  <thead>
    <tr>
      <th style="width: 20%;"></th>
      <th>Quick Test</th>
      <th>Simulation</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td class="axis-cell">Scope</td>
      <td>One record, interactive</td>
      <td>A full sample, as a job</td>
    </tr>
    <tr>
      <td class="axis-cell">Speed</td>
      <td>Instant</td>
      <td>Slower; runs as a queued job</td>
    </tr>
    <tr>
      <td class="axis-cell">Use For</td>
      <td>Sanity-checking an aggregated Data Element while iterating</td>
      <td>Validating performance, generating approval evidence</td>
    </tr>
  </tbody>
</table>

* It works only on **aggregated Data Elements**.
* It runs **Python and pandas** definitions. Test Spark aggregates with a full [Simulation](/user-guide/how-tos/run-a-simulation/) instead.

Other object types (Features, Models, Policies) do not have a Quick Test tab. To trace a Policy record end-to-end, use [Run a Single Record](/user-guide/how-tos/test-a-single-record/) instead.

## How to Run a Quick Test

<details open class="step">
<summary>

#### Open the Quick Test tab

</summary>

Open the aggregated Data Element's details page and switch to the **Quick Test** tab.

If the Data Element is not aggregated, the tab shows **Enable Data Element Aggregation to use Quick Test**. Turn on **Is Aggregated** in the **Details** tab first, then return.

</details>

<details open class="step">
<summary>

#### Enter an ID

</summary>

In **Enter ID to start reviewing**, type the ID of the record you want to test. For an application-level Data Element that is an application ID; for an account-level one, an account ID. The field checks that the value matches the ID column's data type.

Click **Submit & Review**. The platform pulls just that record's rows from the source tables and runs the aggregation on them.

</details>

<details open class="step">
<summary>

#### Read the result

</summary>

The result appears in two parts:

- **Output** - the aggregated value your Data Element returned for that record, shown at the top. Any `print` statements from your definition appear just below it, so you can trace what the logic did.
- **Filtered Data** - the source rows the aggregation read for that record, shown alongside the output, one table at a time. You can sort, filter, and page through each table, or open it in a new tab, to check the aggregation read what you expected.

If your definition errors out, an **Error Logs** section takes the place of the output and shows the traceback.

Adjust the definition and re-run until the output looks right. For example, if a maximum-balance aggregate comes back lower than you expected, open **Filtered Data** to check whether every account row for that application was actually read. Once the logic checks out, move on to a full [Simulation](/user-guide/how-tos/run-a-simulation/).

</details>

## What's Next

- [Register a Data Aggregate](/user-guide/how-tos/register-a-data-aggregate/) to set up the aggregation Quick Test runs on.
- [Run a Simulation](/user-guide/how-tos/run-a-simulation/) once the logic checks out, to validate it across a sample.
- For a Policy, trace a record end-to-end with [Run a Single Record](/user-guide/how-tos/test-a-single-record/).