> For the complete documentation index, see [llms.txt](https://learning.contextqa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learning.contextqa.com/getting-started/interactive-demo.md). # Interactive Demo Explore guided ContextQA product demos for test data, environments, AI-powered automation, and release confidence without creating an account. ## Quick answer These click-through demos let you explore real ContextQA workflows without signing in or changing production data. Each walkthrough explains the user action, the product response, and the business value of the workflow. Use the short tours to evaluate a specific outcome, or open a detailed walkthrough when you want to inspect the complete workflow. ## Choose a demo | Start with | Best for | Outcome | | -------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | -------------------------------------------------------------------------------- | | [Platform capabilities](#explore-contextqa-platform-capabilities) | Evaluation teams comparing automation approaches | See how ContextQA connects test creation, execution, and release evidence | | [API testing overview](/api-testing/api-testing.md#interactive-demo-api-testing-overview) | Developers and SDETs validating services | See how requests, validations, variables, and results fit together | | [Create and execute an API test](/api-testing/creating-api-tests.md#interactive-demo-create-and-execute-an-api-test) | Teams starting API automation | Build, run, and inspect a reusable API test | | [API variables and environments](/api-testing/api-testing-tutorial.md#interactive-demo-use-variables-and-environments-in-api-tests) | Teams moving API tests across approved targets | Keep endpoints, credentials, and runtime values outside the saved request | | [API chaining and tokens](/api-testing/api-chaining.md#interactive-demo-chain-api-calls-and-reuse-a-token) | Teams testing authenticated service journeys | Capture a response value and reuse it in later requests | | [API and UI automation](/business-use-cases/complex-web-and-authentication.md#interactive-demo-connect-api-and-ui-automation) | Teams validating one journey across system layers | Use API setup and browser verification in one continuous flow | | [Mobile testing overview](/mobile-testing/mobile-testing.md#interactive-demo-mobile-testing-overview) | Mobile QA teams evaluating Android and iOS coverage | Understand build, device, execution, and evidence workflows | | [Gesture-based mobile testing](/mobile-testing/creating-mobile-tests.md#interactive-demo-configure-gesture-based-mobile-testing) | Mobile QA teams validating touch interactions | Configure tap, swipe, scroll, pinch, and zoom scenarios | | [First mobile test](/mobile-testing/mobile-testing-tutorial.md#interactive-demo-run-your-first-mobile-test-on-a-real-device) | Teams evaluating the complete device workflow | Follow test creation through real-device execution and evidence | | [Mobile suites and plans](/mobile-testing/mobile-test-plans.md#interactive-demo-organize-mobile-suites-and-plans) | Mobile release owners | Organize stable cases and preserve device-specific plan evidence | | [Jira test generation](/integrations/jira.md#interactive-demo-generate-tests-from-jira) | Teams that manage requirements in Jira | Preserve requirement traceability while generating tests | | [Jira defect reporting](/integrations/jira.md#interactive-demo-report-a-failure-to-jira) | Teams connecting test triage to delivery work | Carry failure evidence and root-cause context into Jira | | [Test suites and plans](/web-testing/managing-test-suites.md#interactive-course-create-suites-and-start-a-test-plan) | Regression and release owners | Organize reusable coverage, configure execution, and run a plan | | [Requirements to generated tests](/business-use-cases/requirements-to-release.md#interactive-demo-requirements-to-generated-tests) | QA teams turning source material into coverage | See the review path from requirement to generated tests in three screens | | [Execution and evidence](/reporting/test-results.md#interactive-demo-execution-to-evidence) | SDETs and release owners investigating test runs | Follow a run from launch to durable evidence in four screens | | [Root cause and impact analysis](/reporting/failure-analysis.md#interactive-course-analyze-root-cause-and-impact) | Teams triaging failed runs | Move from captured evidence to a reviewable AI-assisted assessment | | [Access and system governance](/administration/administration.md#interactive-demo-access-and-system-governance) | Workspace administrators governing teams and settings | Review roles, members, audit activity, and organization settings in four screens | | [Local and global variables](#compare-local-and-global-variables) | Testers and SDETs managing reusable data | Keep case-specific values separate from workspace-wide values | | [Environments and data profiles](#configure-environments-and-data-profiles) | Release teams reusing tests across deployment targets | Keep target configuration and input combinations outside test logic | | [Dynamic data generation](/web-testing/test-data-management.md#interactive-demo-generate-dynamic-test-data) | Teams preventing duplicate test-data collisions | Generate safe runtime values while keeping validations deterministic | | [Self-healing and conditional validation](/web-testing/self-healing.md#interactive-demo-self-healing-and-conditional-validation) | Teams reducing routine locator maintenance | See how ContextQA repairs UI drift without hiding real failures | | [Conditions and loops](/web-testing/test-steps-editor.md#interactive-demo-conditions-and-loops) | SDETs building data-dependent workflows | Model branches and repeated actions without duplicating tests | | [Knowledge Base context](/ai-features/knowledge-base.md#interactive-demo-give-the-ai-agent-application-context) | Teams teaching the agent application conventions | Reuse governed guidance without copying it into every test | | [Salesforce automation](/salesforce-testing/salesforce-testing.md#interactive-demo-salesforce-automation-overview) | Salesforce QA and release teams | See resilient Lightning automation, data, execution, and evidence | | [First Salesforce test](/salesforce-testing/test-generation-and-execution.md#interactive-course-create-and-run-your-first-salesforce-test) | SDETs beginning Salesforce automation | Create and run a reusable Salesforce test in two segments | | [Salesforce API and UI validation](/business-use-cases/salesforce-and-enterprise-workflows.md#interactive-demo-connect-salesforce-api-and-ui-validation) | Enterprise teams validating cross-layer outcomes | Combine fast API setup with user-visible Salesforce verification | {% hint style="info" %} No ContextQA account is required. The demos use guided, non-destructive screens and do not expose customer credentials or production test data. {% endhint %} ## Explore ContextQA platform capabilities Start here for an end-to-end orientation. The walkthrough connects the major stages of the ContextQA workflow so an evaluation team can decide which feature guide to explore next. {% embed url="" %} ### What to notice * ContextQA brings test design, execution, and result review into one governed workflow. * Guided screens let stakeholders evaluate the user experience without accessing a live workspace. * The final call to action opens a tracked request for a tailored evaluation. ## Compare local and global variables Use this demo when one test must combine case-specific values with approved data shared across a workspace. It shows how ContextQA keeps each scope explicit so teams can reuse data without coupling unrelated tests. {% embed url="" %} ### What to notice * Local variables keep temporary or case-specific values close to the test that owns them. * Global variables and data profiles provide controlled reuse across tests. * Clear scope reduces duplicated setup, maintenance effort, and accidental data conflicts. ## Configure environments and data profiles Use this demo to see how target-specific configuration and reusable data sets remain separate from test logic. The same test can then run against approved targets and input combinations without duplicating its steps. {% embed url="" %} ### What to notice * Environments keep URLs and target-specific configuration out of test steps. * Test data profiles let one test cover multiple data combinations. * Selecting configuration at execution time keeps the saved test portable and reviewable. Read the complete guides to [test data](/web-testing/test-data-management.md) and [environment management](/web-testing/environment-data-management.md). ## How to use these demos {% hint style="warning" %} Any username, password, token, payment value, or one-time code visible in a captured demo is illustrative test data only. It is not a reusable ContextQA login and does not grant access to the captured workspace. Do not copy it into your application; use your own approved evaluation credentials. {% endhint %} 1. Choose the workflow closest to the problem you are solving. 2. Follow the highlighted action in each step; use full-screen mode when available. 3. Open the linked guide for prerequisites, detailed instructions, and verification criteria. 4. Use the final call to action to evaluate the same workflow with your application and team. ## Frequently asked questions ### Is this a video or a live product trial? It is an interactive product walkthrough. You control the pace and follow guided actions on captured ContextQA screens, so you can understand the workflow without provisioning a workspace. ### Do I need a ContextQA account? No. These demos are publicly viewable and do not require credentials. A ContextQA workspace is needed only when you want to create, execute, and manage your own automated tests. ### Can I use credentials shown inside a demo? No. Values visible in a Storylane screen are captured examples, not live credentials or a shared trial account. The interactive embed also does not sign you in to the ContextQA portal. [Book a demo](https://contextqa.com/book-a-demo/?utm_source=learning.contextqa.com\&utm_medium=interactive_demo\&utm_campaign=storylane_docs\&utm_content=demo_credentials_faq) when you need an evaluation workspace or access instructions. ### Can ContextQA use my application and test data? Yes. During an evaluation, ContextQA can be configured for your application, environments, reusable data, browser or device coverage, and governance requirements. The public demos intentionally use safe example data. ### Where can I learn the full workflow? Every demo links to its corresponding documentation page. The documentation explains prerequisites, field behavior, expected results, limitations, and related capabilities in a format that both people and AI assistants can retrieve and cite. ## Evaluate ContextQA with your application See how the same reusable-data and environment patterns apply to your release process, then expand into AI-authored tests, cross-browser execution, evidence, and reporting. {% hint style="success" %} [Book a ContextQA demo →](https://contextqa.com/book-a-demo/?utm_source=learning.contextqa.com\&utm_medium=interactive_demo\&utm_campaign=storylane_docs\&utm_content=demo_hub_end) {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://learning.contextqa.com/getting-started/interactive-demo.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.