ktm tests inspect
Full test definition with actions, dependencies, and configuration
Full test definition with actions, dependencies, and configuration
Usage
ktm tests inspect <id> [flags]
Examples
# Inspect test as JSON (full definition with actions)
ktm tests inspect 16480
# Inspect test as table (structured summary)
ktm tests inspect 16480 -o table
Arguments
| Argument | Required |
|---|---|
id | Yes |
Details
Fetch the complete test object by ID, including the full actions array (step-by-step test logic), dependencies, monitors, browser config, environment, and all metadata.
This returns significantly more data than "tests get", which only fetches variable definitions. Use "tests inspect" when you need to understand the test logic itself.
Notes
- Full test definition (actions, dependencies, configuration). If you only need the variables and owners to build a campaign,
ktm tests getis faster.
Related
Global flags (--output, --debug, --host, …) apply to every command. See the command reference overview.
What's next?
Last updated on