docs(tests): fix Test-page navigation now that Test moved off the sidebar

Author: isshaddad

docs/guides/examples/sentry-error-tracking.mdx

@@ -169,7 +169,7 @@ After creating the task, deploy your project.
 
     </CodeGroup>
 
-Once deployed, navigate to the `test` page in the sidebar of your [Trigger.dev dashboard](https://cloud.trigger.dev), click on your `prod` environment, and select the `sentryErrorTest` task.
+Once deployed, open the `sentryErrorTest` task in your [Trigger.dev dashboard](https://cloud.trigger.dev) (make sure you're in your `prod` environment) and press the "Test" button to open the test page for it.
 
 Run a test task with an empty payload by clicking the `Run test` button.
 

docs/images/test-dashboard.png

@@ -3,18 +3,19 @@ title: "Run tests"
 description: "You can use the dashboard to run a test of your tasks."
 ---
 
-From the "Test" page in the side menu of the dashboard you can run a test for any of your tasks from any environment.
+You can run a test for any of your tasks, in any environment, from the dashboard.
 
-![Select an environment](/images/test-dashboard.png)
+<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>
 
-<Icon icon="circle-1" iconType="solid" color="#FF2D6B" size="20" /> Select a task to test
+On a task's test page you can:
 
-<Icon icon="circle-2" iconType="solid" color="#FF2D6B" size="20" /> Include a payload or metadata
+- 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.
 
-<Icon icon="circle-3" iconType="solid" color="#FF2D6B" size="20" /> Configure any additional options like the machine size, queue or delay
-
-<Icon icon="circle-4" iconType="solid" color="#FF2D6B" size="20" /> Select from previous test runs
-
-<Icon icon="circle-5" iconType="solid" color="#FF2D6B" size="20" /> Save the current test configuration as a template for later
-
-<Icon icon="circle-6" iconType="solid" color="#FF2D6B" size="20" /> Run the test
+![Test page](/images/test-dashboard.png)

docs/run-tests.mdx

@@ -1,12 +1,10 @@
 <Step title="Perform a test run using the dashboard">
 
-The CLI `dev` command spits out various useful URLs. Right now we want to visit the Test page.
+The CLI `dev` command spits out various useful URLs, including a link to the dashboard. Open it, find your Example task on the Tasks page, and press the "Test" button to open its test page.
 
-You should see our Example task in the list <Icon icon="circle-1" iconType="solid" size={20} color="F43F47" />, select it. Most tasks have a "payload" which you enter in the JSON editor <Icon icon="circle-2" iconType="solid" size={20} color="F43F47" />, but our example task doesn't need any input.
+Most tasks have a "payload" which you enter in the JSON editor, but our example task doesn't need any input. You can also configure run options, pre-populate the form from recent runs, and save run templates.
 
-You can configure options on the run <Icon icon="circle-3" iconType="solid" size={20} color="F43F47" />, view recent payloads <Icon icon="circle-4" iconType="solid" size={20} color="F43F47" />, and create run templates <Icon icon="circle-5" iconType="solid" size={20} color="F43F47" />.
-
-Press the "Run test" button <Icon icon="circle-6" iconType="solid" size={20} color="F43F47" />.
+Press the "Run test" button.
 
 ![Test page](/images/test-dashboard.png)