Files
triggerdotdev--trigger.dev/docs/v3/run-tests.mdx
T
Matt Aitken de302858f8 v3 docs (#929)
* Started building out the docs navigation

* Drafted out a lot of the docs pages. With just titles and descriptions with a coming soon message for now.

* A ton more scaffolded pages with titles, descriptions, coming soon/incomplete docs messages

* Created the remaining page stubs

* Introduction page improvements

* Lots of docs changes, mostly the task overview page

* Moved some bits around

* Task overview fleshed out

* Triggering docs page

* Regular task page

* CLi dev docs

* Docs for debugging locally

* Environment variables docs

* Added env var images

* Deployment guides

* Updated the title of “Integrations” to “Deployment integrations” to make it less confusing

* Lots more docs pages

* Changed the language to JavaScript

* Fixed typos about queues and added a simple code sample

* Moved the local debugger docs into the CLI dev page

* Added the CLI deploy options

* Delete the local debugger page

* Updated the logging page with structured logging

* Added the new CLI deploy options

* Change to h4 for one of the options

* Errors page

* WIP on retrying

* Retrying guide

* Wait docs pages

* Queuing docs simplified, partial written

* Queuing and concurrency docs

* Run tests docs

* New combined error and retrying page

* Errors and retrying page updated

* More docs

* Added a possible configurations coming soon table

* Created a limits page

* Added warnings about how you need to get early access

* Minor fixes for the docs
2024-03-22 14:09:27 +00:00

27 lines
873 B
Plaintext
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
title: "Run tests"
description: "You can use the dashboard to run a test of your tasks."
---
From the "Test" page in the sidebar of the dashboard you can run a test for any of your tasks, that includes for any environment.
<Steps>
<Step title="Select an environment">
![Select an environment](/images/v3/test-select-environment.png)
</Step>
<Step title="Select the task to test">
![Select the task to test](/images/v3/test-select-task.png)
</Step>
<Step title="Enter a payload">
Select a recent payload as a starting point or enter from scratch. Payloads must be valid JSON you will see helpful errors if it is not. Press the "Run test" button or use the keyboard shortcut to run the test.
![Enter a payload](/images/v3/test-set-payload.png)
</Step>
<Step title="View the run live">![View the run live](/images/v3/run-in-progress.png)</Step>
</Steps>