> 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/video-walkthroughs.md).
# Video Walkthroughs
## Quick answer
Task-focused ContextQA walkthroughs for web, mobile, API, requirements, test data, Jira, dashboards, suites, and plans. Use this page to preview the workflow and its visible results before following the linked written instructions.
## What this page covers
Use this library when you want to watch a complete workflow before following the written guide. Each recording opens in Google Drive's public preview player and is paired with the business outcome it supports and the detailed documentation to use as a reference.
The written summaries below are also the searchable companion to the recordings. Use them to choose a walkthrough, understand its outcome without playing the video, and continue into a complete step-by-step guide.
{% hint style="info" %}
The source folder contains older recordings of several workflows. To avoid conflicting instructions, this page links the corresponding recording from **Updated video** whenever one exists. Two older recordings are included because they uniquely cover the dashboard and Excel test-case import.
{% endhint %}
## Getting started and web testing
| Walkthrough | Business use case | Written guide |
| --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------- |
| [Generate and execute your first web test](https://drive.google.com/file/d/1QBow6jtlcI8JBbJ9mMZNLTywb_zTab1m/preview) | Turn a plain-English user journey into a runnable browser test without writing automation code. | [Quickstart](/getting-started/quickstart.md) |
| [Reuse test-case prerequisites](https://drive.google.com/file/d/12Vvu28Pv9aUWGjXO3Lnd8J2Ma9iGTIRb/preview) | Reuse login or setup once instead of copying it into every dependent test. | [Creating test cases](/web-testing/creating-test-cases.md) |
| [Record and play a browser flow](https://drive.google.com/file/d/13Gab4J-oTb7XZVNxAZJNpDvXme-nE-iX/preview) | Convert an exploratory browser session into a repeatable regression test. | [Record your first test](/web-testing/recording-tutorial.md) |
| [Generate tests from requirements](https://drive.google.com/file/d/1JtdXOKBYGoQiGa4woSapLiVOge0vrlyS/preview) | Convert requirement files into reviewable positive, negative, boundary, validation, functional, and end-to-end coverage. | [Generate tests from requirements](/ai-features/generate-tests-from-requirements-tutorial.md) |
| [Generate runnable tests from Jira](https://drive.google.com/file/d/1v3KHLYP17reGp1BZDSOOxGF5MAsLuTF_/preview) | Keep ticket context and generated tests traceable to the same delivery source. | [Jira integration](/integrations/jira.md) |
| [Choose local or global variables](https://drive.google.com/file/d/1iX_UkzEWYG52QiNoIl7em5qnNrxV7oeW/preview) | Keep one-off values inside a test while managing shared values once for the workspace. | [Test data management](/web-testing/test-data-management.md) |
| [Configure environments and data profiles](https://drive.google.com/file/d/1UbcQCoDLHLrjbau3Jfb9HqGF3lnsGR-m/preview) | Run the same flow against different deployment targets and data rows without duplicating tests. | [Environment and data management](/web-testing/environment-data-management.md) |
| [Organize tests with suites and plans](https://drive.google.com/file/d/1sZGxrvhFYCIyAL5iKCOi6y7upmpluS-2/preview) | Group coverage by purpose, then control where, how, and when it runs. | [Test plans](/web-testing/test-plans.md) |
| [Import test cases from Excel](https://drive.google.com/file/d/1sP-9thppLX1NcEb5tI5471jaICkfMoqI/preview) | Migrate an existing manual test inventory and optionally organize it into a suite and plan. | [Creating test cases](/web-testing/creating-test-cases.md#import-test-cases-or-requirements) |
| [Understand dashboard analytics](https://drive.google.com/file/d/12ulnwgfotrp_vy0SSlmVs9DUVeX5McY_/preview) | Review execution, source, coverage, risk, and activity trends from a single operational view. | [Analytics dashboard](/reporting/analytics-dashboard.md) |
### What the web-testing walkthroughs cover
* **First web test:** describe a user journey, generate a runnable browser test, execute it, and review its result.
* **Prerequisites:** place shared setup or login behavior in a prerequisite so dependent tests do not repeat the same steps.
* **Record and Play:** capture a browser interaction and convert it into reusable test steps.
* **Requirements and Jira:** turn an existing delivery artifact into proposed test coverage, then review the generated cases before execution.
* **Variables, environments, suites, and plans:** separate reusable data and execution configuration from the test's business flow.
* **Excel import and analytics:** migrate existing cases and use reporting to understand execution and coverage trends.
## Mobile testing
| Walkthrough | Business use case | Written guide |
| ------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| [Mobile testing overview](https://drive.google.com/file/d/1wAtefl0InGTTJ3Gq5qPckIBvkwCZo3uh/preview) | Understand how app builds, real devices, AI-assisted generation, and execution evidence fit together. | [Mobile testing overview](/mobile-testing/mobile-testing.md) |
| [Upload, configure, and run your first mobile test](https://drive.google.com/file/d/1jEH39OreAYE9eJYf3fpDFFek5wl4M-WO/preview) | Validate an Android APK or iOS IPA on a selected real device. | [Create and run mobile tests](/mobile-testing/creating-mobile-tests.md) |
| [Test tap, swipe, scroll, pinch, and zoom](https://drive.google.com/file/d/1-2B2YsEDjeadues_CsWehVUutsPKdpTk/preview) | Cover touch interactions that desktop-style click tests cannot represent. | [Gesture-based scenarios](/mobile-testing/creating-mobile-tests.md#gesture-based-mobile-scenarios) |
| [Run Android and iOS suites in a test plan](https://drive.google.com/file/d/1nS5FIKuOMw2oHlaWSan2n-J6WpYy-YYi/preview) | Execute platform-specific suites together and compare results in one plan report. | [Mobile test plans](/mobile-testing/mobile-test-plans.md) |
### What the mobile-testing walkthroughs cover
* **Mobile overview:** connect uploaded builds, device selection, AI-assisted test creation, and execution evidence.
* **First mobile test:** upload or select an app build, choose a compatible device, generate a test, and review its run.
* **Gestures:** represent touch-specific actions such as tap, swipe, scroll, pinch, and zoom.
* **Mobile plans:** group Android and iOS coverage into suites and run them through a repeatable plan.
## API testing
| Walkthrough | Business use case | Written guide |
| ------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | -------------------------------------------------------- |
| [API testing overview](https://drive.google.com/file/d/1KHQnWchIXiVLFka7a0ZGrtgYJw7Mt0hy/preview) | Validate backend behavior earlier and combine API checks with end-to-end UI coverage. | [API testing overview](/api-testing/api-testing.md) |
| [Create your first API test](https://drive.google.com/file/d/1OyuSh20YojL-qkQs9-5rG2yYR4YqjQ98/preview) | Configure a request, store its response, assert the status, and inspect the run history. | [Creating API tests](/api-testing/creating-api-tests.md) |
| [Chain API requests](https://drive.google.com/file/d/1zU67osZy0xyo7pTme0wy8720FsHx0QU1/preview) | Capture a live authentication token and pass it safely into a dependent request. | [API chaining](/api-testing/api-chaining.md) |
### What the API-testing walkthroughs cover
* **API overview:** understand where request steps, response variables, validations, and hybrid API-plus-UI flows fit.
* **First API test:** configure a request, store its response, add an assertion, and inspect the execution result.
* **API chaining:** extract a value from one response and reuse it in a later request without hardcoding a runtime token.
## Frequently asked questions
Which walkthrough should a new ContextQA user watch first?
Start with **Generate and execute your first web test** if you test a browser application, **Upload, configure, and run your first mobile test** for an Android or iOS app, or **Create your first API test** for a REST API. Continue with the written guide beside the selected video.
Can I understand a walkthrough without watching the video?
Yes. Each recording has a written business outcome and a related guide. The section summaries describe the workflow in text, while the written guide provides the detailed instructions.
Why does a video open in Google Drive?
The recordings are hosted in Google Drive and link directly to its public preview player. If a player is blocked by your browser or network, use the paired written guide or open the complete source folder.
Are the videos or written guides the authoritative instructions?
Use the written guide as the maintained reference for current user-facing behavior. The video demonstrates the workflow visually, while the written guide is easier to update when labels, navigation, or available options change.
If a player does not open, check whether your browser or network blocks Google Drive. You can also open the [complete source video folder](https://drive.google.com/drive/folders/1bRDzkQHTgqATstdfZBAZsnjr_ehEBADr) to access the original recordings.
## Want a walkthrough tailored to your workflow?
The recordings demonstrate standard workflows. For a guided walkthrough using your application, platform, and testing priorities, book a personalized session with the ContextQA team.
[**Book a Demo →**](https://contextqa.com/book-a-demo/)
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://learning.contextqa.com/getting-started/video-walkthroughs.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.