Managing Test Cases

​

Editing a Single Test Case

Verify user can log in with valid credentials.

Verify the Sign In link directs users to the login page, that
submitting email "test@example.com" + password "test123" lands them
on the dashboard, and that the navbar avatar shows after login.

​

Editing steps

​

Asking AI for a Fix

​

Batch Editing

• Form mode
• YAML mode

Every case as a row with test name, priority, description, and each flow step editable in place. Best for touching a handful of cases in context.Save writes only the rows you changed and reports per case if any row fails, so a partial save never silently loses the rest.

The whole plan as one YAML document. Best for sweeping edits: renumbering steps across many cases, find-and-replace on a URL, or pasting cases between projects.

useCases:
  - useCase: Authentication
    slug: authentication
    testCases:
      - id: TC001
        priority: High
        name: Login with valid credentials
        description: Verify that submitting valid credentials lands the
          user on the dashboard.
        steps:
          - Navigate to the login page
          - Enter "user@example.com" and the test password
          - Click the Sign In button
          - assert: The dashboard page is displayed

The rules (also in the editor’s header comment):

• A plain step line is an action; assert: ... marks an assertion.
• Add a case by copying an existing one and removing its id line.
• Remove a case by deleting its block.
• Leave id and slug values as they are; they map your edits back to existing cases.

​

Adding Test Cases

• Add Tests with AI: describe what you want covered (optionally scoped to one use case), and TestSprite’s testing agent proposes a batch. Before anything is created, you can edit each proposal’s title, description, priority, and steps, untick the ones you don’t want, or hand-add rows.
• Add Test Manually: a form with use case, title, priority, description, and a step list (action or assertion per step).

​

Regenerating from Sources

​

Deleting Test Cases

• One case: the trash icon in its drawer, or the row’s context menu. A case that has never run is labeled “Remove from plan”; one with run history warns you the history goes with it.

• Many cases: select rows and use the trash button in the toolbar.

​

Where to Go Next