# Form/page reference Many TestVibe screens include contextual help links. These pages explain the purpose of the form, the common tasks it supports, and the controls that matter most. ## Help URL Pattern Form help pages use stable paths: | Form | Help path | | ----------------------------- | ------------------------------------------------ | | Login | `/reference/forms/login` | | Run | `/reference/forms/run` | | Project | `/reference/forms/project` | | Playwright test configuration | `/reference/forms/playwright-test-configuration` | | Test failure details | `/reference/forms/test-failure-details` | The full index is [Form Help Pages](/reference/forms.md). ## Common Form Help Pages
Sign in and setupLogin, SelectInstallation, SelectRepository, ProjectSetup
Author testsTest, Editor, Prompt, TestPlanner
Generate and runRecentTestGenerations, Run, PlaywrightTestConfiguration
Review evidenceTestFailureDetails, TestResultsPopup, Picture, Video, NetworkDetails
Settings and accountAccount, ApiKeys, Team, Usage
## Stable Links Help paths should stay stable even when the app changes. If a form is renamed in the product, keep the existing help page and update the content so old links do not break. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.testvibe.com/reference/form-page-reference.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.