> ## Documentation Index
> Fetch the complete documentation index at: https://docs.galileo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Step 2 — Test set

> Pick or upload the labelled dataset Luna Studio will evaluate the fine-tuned metric against.

The test set is the **ground truth** for the run. After training, Luna Studio scores the resulting metric against this dataset and reports F1, AUC-ROC, and other result metrics on the Run details page.

<Frame caption="Step 2 — pick an existing test set or add a new one">
  <img src="https://mintcdn.com/v2galileo/-aQkdd7oOglUYIo1/images/luna-studio/runs/new-run-test-set.png?fit=max&auto=format&n=-aQkdd7oOglUYIo1&q=85&s=cc1f7b4b85f4c158b1691bef7d1f60f1" alt="Test set step" width="1024" height="659" data-path="images/luna-studio/runs/new-run-test-set.png" />
</Frame>

## Pick an existing test set

The **Test set** select shows test sets already added to your organization. Each option includes a row count and source label, e.g. `rag-eval-dataset-v2 — 320 rows · Uploaded`.

Type into the select to filter by name.

## Add a new test set

If you don't have one yet, click the dropdown's **Add new test set** action. The **Add test set** modal opens.

The modal title is **Add test set** with the subtitle "Test sets are curated labelled examples used to evaluate your metric." Three sources are available — see [Add a dataset](/luna-studio/ui/datasets/add-a-dataset) for a complete reference.

<CardGroup cols={3}>
  <Card title="Upload from local" icon="upload">
    Drag-and-drop a `.csv` or `.jsonl` file. Use CSV for end-to-end run processing.
  </Card>

  <Card title="Fetch from URL" icon="link">
    Paste a publicly reachable or pre-signed `http://` or `https://` URL.
  </Card>

  <Card title="Import from Galileo" icon="cloud-arrow-down">
    Browse datasets in your connected Galileo workspace.
  </Card>
</CardGroup>

Required columns depend on the metric shape. For details, see [Prerequisites](/luna-studio/ui/prerequisites).

Test sets must contain at least 300 rows total and at least 100 examples per class.

<Warning>The source picker accepts JSONL during ingestion, but current metric-aware validation reads the stored file as CSV. Convert JSONL to CSV before using it as the run's test set.</Warning>

<Note>Importing from Galileo requires a deployment-configured [Galileo API connection](/luna-studio/ui/integrations/galileo). If an inline prompt does not clear the backend error, ask your deployment operator to configure the URL and key.</Note>

## Validation

Because this flow has the selected metric as context, Luna Studio validates the test set's shape-specific columns, label type, and row thresholds before attaching it to the run. If there are validation errors, they are highlighted. The uploaded dataset can remain available on the global Datasets page even when it is rejected for this run.

<Frame caption="Step 2 with a validation error — the flow blocks Next until the schema is valid">
  <img src="https://mintcdn.com/v2galileo/-aQkdd7oOglUYIo1/images/luna-studio/runs/new-run-test-set-error.png?fit=max&auto=format&n=-aQkdd7oOglUYIo1&q=85&s=3b719385afe2e59efee5d94f0045cb47" alt="Test set validation error" width="1024" height="659" data-path="images/luna-studio/runs/new-run-test-set-error.png" />
</Frame>

## Dataset preview

If validation completes, you should see a preview of the test set rows.

The preview is paginated so you can inspect rows without leaving the run creation flow.

<Tip>Use the **Calculate F1 score** button to see the F1 score of your LLM-as-judge prompt on the selected test set. This is your benchmark score which Luna Studio will aim to achieve with a Luna metric.</Tip>

## Where to go next

<CardGroup cols={2}>
  <Card title="Step 3 — Training set" icon="dumbbell" href="/luna-studio/ui/runs/new-run/step-3-training-set">
    Generate from the test set, or upload your own.
  </Card>

  <Card title="Add a dataset" icon="database" href="/luna-studio/ui/datasets/add-a-dataset">
    Reference for all three dataset sources.
  </Card>
</CardGroup>
