Iss
9f4d8d8b0c
The dashboard was redesigned and two pages moved, but the docs still described the old sidebar: - **Schedules** no longer has its own sidebar page — schedules are managed from the **Tasks** page (open a scheduled task to create / view / edit / enable-disable / delete them). - The standalone list-based **Test** page is deprecated — you test a task from its own **Test** button now. ## Changes - `tasks/scheduled.mdx`: rewrote the "attaching schedules" and "testing schedules" sections for the Tasks-based flow, added a "managing schedules in the dashboard" section, and added explicit callouts noting both pages moved (so readers — and search — aren't pointed at a page that no longer exists). Re-shot the four schedule screenshots and fixed a mislabeled alt text. - `run-tests.mdx`, `snippets/step-run-test.mdx`, `guides/examples/sentry-error-tracking.mdx`: replaced "select the Test page in the sidebar" with the task-first flow plus a callout, and refreshed `test-dashboard.png`. TRI-11939
22 lines
907 B
Plaintext
22 lines
907 B
Plaintext
---
|
|
title: "Run tests"
|
|
description: "You can use the dashboard to run a test of your tasks."
|
|
---
|
|
|
|
You can run a test for any of your tasks, in any environment, from the dashboard.
|
|
|
|
<Note>
|
|
There is no longer a "Test" page in the sidebar. You test a task from the task itself: on the
|
|
Tasks page open a task (or use the "Test" action next to a task in the Runs list) and press the
|
|
"Test" button to open its test page.
|
|
</Note>
|
|
|
|
On a task's test page you can:
|
|
|
|
- Enter the run's input — a JSON **payload** and optional **metadata**. Scheduled tasks show timestamp fields instead of a payload.
|
|
- Configure run **options** like the machine size, version, queue, tags, retries, max duration, or a delay.
|
|
- Pre-populate the form from a previous run with **Recent runs**, or save and reuse a configuration with **Templates**.
|
|
- Press **Run test** to trigger the run.
|
|
|
|
|