Help URL Index
Stable URL conventions for TestVibe contextual help pages.
TestVibe in-app help links should point to stable paths on https://docs.testvibe.com.
Forms
For Wisej forms, use:
URL path:
/reference/forms/<slug>Where
<slug>is the form class name converted to kebab-case.
Examples:
Login->/reference/forms/loginApiKeys->/reference/forms/api-keysPlaywrightTestConfiguration->/reference/forms/playwright-test-configuration
(Each form page also states its own canonical path in a Help URL line — that line is the source of truth.)
App Views
Dashboard
/workspace/dashboard
Features (Test Suite)
/create-tests/test-suite-overview
Group detail
/create-tests/create-groups-and-tests
Feature or test detail
/create-tests/edit-test-content
Runs
/run-tests
Create run detail
/run-tests
Run detail (terminal)
/results
Run live status
/run-tests/understand-live-run-status
Live Servers
/workspace/live-servers
Load Testing
/load-testing
Load run results
/load-testing/run-a-load-test-and-read-results
Assistant
/assistant
Plugins
/skills/manage-skills
Automations
/run-tests/automations
App Code
/codebase
Generation drawer
/ai-generation/review-generation-progress
Setup wizard
/quickstart
New project
/workspace/create-new-project
Members & access
/workspace/manage-teams-and-members
Settings Panels
Profile
/account-settings/account-settings
Members
/account-settings/team-settings
Tunnels
/account-settings/tunnel-devices
Billing
/account-settings/usage
Credit Usage
/account-settings/credit-usage
Storage
/account-settings/storage
Plans
/pricing/plans
CLI & API keys
/account-settings/api-keys
App Repository
/account-settings/repository-settings
Environments
/workspace/configure-site-url-and-repository
Assets
/account-settings/project-settings
AI Model
/ai-generation/choose-agent-and-model
Variables & Secrets
/workspace/add-api-keys-and-secrets
Notes
/account-settings/notes
Telemetry
/load-testing/server-telemetry
Playwright
/run-tests/browser-viewport-configuration
Notes
Keep URLs stable: prefer updating content over renaming files. The Plugins pages intentionally keep their original
/skills/...paths.If a form, control, or panel name must change, keep the old page or add a redirect in the hosting layer.
Example: the Memories → Notes rename (#836) moved this page to
/account-settings/notes;.gitbook.yamlredirects the old/account-settings/memoriespath here so existing bookmarks and the in-app Help link (which still points at the pre-rename path) don't 404.Use Form/page reference and Form Help Pages to find existing paths before adding a new one.
Last updated
Was this helpful?
