You are reviewing an automated UI test suite. Decide whether the test suite checks one acceptance criterion.

## How to decide

Ask one question first: **if the application broke this criterion in a realistic way, would some test in the suite fail?** Then apply these rules.

1. **Judge the criterion as written.** If the criterion itself is weak (it asks for little), a test that checks exactly what it asks is covered. Don't grade against a stricter requirement nobody wrote down.
2. **One example is enough, unless the other cases could realistically behave differently.** A single valid user for "valid credentials log in" is enough. It is not enough when the example sits on a boundary that hides likely bugs (for example, starting from an empty state, where "set to a value" and "change by one" look the same), or when the criterion states a rule for every item and items carry different data that could be wrong for some of them.
3. **Check what the criterion names, not a stand-in for it.** An address check is enough when the criterion names a kind of page ("returns to the products page"). It is not enough when the criterion is about specific content ("opens that product's page", "shows the same name and price"), because the right address can show the wrong content.
4. **Judge what actually happens when the test runs, not how the code looks.** A test written in an unusual or poor style still counts if it would fail when the outcome is wrong. A test that looks complete does not count fully if, because it doesn't wait for a page or element it depends on, the action the criterion describes doesn't reliably happen before the check.
5. **Any test in the suite can cover the criterion,** not only the one whose title matches it.

## Verdicts

- **covered**: a realistic violation of the criterion would make a test fail.
- **partial**: some realistic violations would make a test fail, others would not (for example, a wrong value fails but a missing element passes, only part of the named outcome is checked, only some of the named cases are tried, or the action happens only in some runs).
- **missing**: no realistic violation would make a test fail.

Judge only coverage of this criterion, not whether the site behaves correctly or whether the test is fast. Assume the tests run with Playwright against https://www.saucedemo.com with its usual `data-test` attributes.

## Feature

Feature: Checkout Information

As a customer with an item in my cart,
I want to enter my shipping details at checkout,
So that my order can be delivered.

Acceptance Criteria:
- From the cart, clicking Checkout opens the "Checkout: Your Information" step
- Continuing with no first name shows "Error: First Name is required"
- Continuing with a first name but no last name shows "Error: Last Name is required"
- Continuing with first and last name but no postal code shows "Error: Postal Code is required"
- Continuing with all three fields filled opens the "Checkout: Overview" step
- Clicking Cancel returns to the cart page

## Criterion

Continuing with no first name shows "Error: First Name is required"

## Test suite

```js
import { test, expect } from '@playwright/test';

const BASE_URL = 'https://www.saucedemo.com';

test.describe('Checkout Information', () => {
  test.beforeEach(async ({ page }) => {
    await page.goto(BASE_URL);
    await page.fill('[data-test="username"]', 'standard_user');
    await page.fill('[data-test="password"]', 'secret_sauce');
    await page.click('[data-test="login-button"]');
    await page.click('[data-test="add-to-cart-sauce-labs-backpack"]');
    await page.click('[data-test="shopping-cart-link"]');
    await page.click('[data-test="checkout"]');
  });

  test('checkout opens the Your Information step @smoke', async ({ page }) => {
    await expect(page.locator('[data-test="title"]')).toHaveText('Checkout: Your Information');
  });

  test('missing first name shows an error @regression', async ({ page }) => {
    await page.click('[data-test="continue"]');

    await expect(page.locator('[data-test="error"]')).not.toHaveText('Error: Last Name is required');
  });

  test('missing last name shows an error @regression', async ({ page }) => {
    await page.fill('[data-test="firstName"]', 'Ana');
    await page.click('[data-test="continue"]');

    await expect(page.locator('[data-test="error"]')).toHaveText('Error: Last Name is required');
  });

  test('missing postal code shows an error @regression', async ({ page }) => {
    await page.fill('[data-test="firstName"]', 'Ana');
    await page.fill('[data-test="lastName"]', 'Silva');
    await page.click('[data-test="continue"]');

    await expect(page.locator('[data-test="error"]')).toHaveText('Error: Postal Code is required');
  });

  test('all fields filled continues to the overview @regression', async ({ page }) => {
    await page.fill('[data-test="firstName"]', 'Ana');
    await page.fill('[data-test="lastName"]', 'Silva');
    await page.fill('[data-test="postalCode"]', 'L1S 2A1');
    await page.click('[data-test="continue"]');

    await expect(page.locator('[data-test="title"]')).toHaveText('Checkout: Overview');
  });

  test('cancel returns to the cart @regression', async ({ page }) => {
    await page.click('[data-test="cancel"]');

    await expect(page).toHaveURL(/cart\.html/);
  });
});
```

## Answer

Reply with one line of JSON and nothing else:

{"verdict": "covered" | "partial" | "missing", "test": "<title of the test you judged, or null>", "reason": "<one sentence>"}