# Uploaded Test Files {% hint style="info" %} **Who is this for?** QA engineers and test managers who import requirements documents into ContextQA and need to review, filter, and manage the generated test cases. {% endhint %} ## Overview When you import a requirements file (Excel spreadsheet, video, JSON, or Figma design) using the **Import File** method in the [test case creation dialog](/web-testing/creating-test-cases.md), ContextQA processes the file and generates test cases automatically. The **Uploaded Test Files** section provides a dedicated view for managing these imported files and their generated test cases. The detail view for each uploaded file includes six tabs: | Tab | Purpose | | ----------------- | ---------------------------------------------------------------- | | **Test Cases** | Browse, search, filter, and manage generated test cases | | **Questionnaire** | Review and answer AI-generated questions about your requirements | | **AI Analysis** | View AI-powered analysis of the uploaded file | | **Gaps** | Identify coverage gaps in the generated test cases | | **Metadata** | View file metadata and upload details | | **History** | Track changes to the uploaded file (coming soon) | *** ## Opening uploaded test files 1. Navigate to **Test Development** from the left sidebar. 2. Select **Imported Files** from the navigation. The imported files list displays all uploaded requirement files. Each row in the list shows: | Column | Description | | ------------------ | ----------------------------------------------------- | | **ID** | Unique identifier for the uploaded file | | **Name** | File name | | **Type** | File format (Excel, CSV, etc.) | | **Status** | Processing status — Completed, Pending, or Processing | | **Estimated Time** | Estimated processing time | | **Test Cases** | Number of generated test cases | | **Created By** | Team member who uploaded the file | | **Created Date** | Upload timestamp | Click any row to open the file detail view. *** ## File detail view The detail view header displays: * **File name** and **status badge** * **File type** and **test type** labels * **Requirement code** identifier * **Created by** and **date** information * **Test case count** badge * **Export** button to download generated test cases * **Add More Context** button to provide additional information for AI generation ### Test cases tab The default tab displays all test cases generated from the uploaded file in a searchable, filterable table. **Search and filter:** * Use the search bar to find test cases by name or description * Click the **Filter** button to open the filter panel with options for status, type, and other attributes * Active filters appear as removable chips above the table **Table columns:** Each test case row displays the name, steps count, variables, and status. Click a row to open the **test case detail drawer** on the right side, which shows: * Test case title and description * Full step list with actions and expected results * Variables used in the test case * **Approve** and **Reject** actions for reviewing generated test cases * **Save** to persist changes **Bulk actions:** Select multiple test cases using the checkboxes to access bulk operations from the toolbar. **Generation in progress:** If the AI is still generating test cases, a progress indicator displays: * Progress percentage and estimated time remaining * A message that generation runs in the background and you can continue working ### Questionnaire tab After generating test cases from a requirements file, the AI may identify areas where additional context is needed. The questionnaire tab displays these questions. * Review each question and provide answers in the input fields * Answers help the AI refine and improve the generated test cases * Skipped questions display a note indicating they were not answered ### AI analysis tab Displays AI-powered analysis of the uploaded file content. This tab provides insights about the requirements document, including coverage assessment, complexity analysis, and recommendations for test case generation. ### Gaps tab Identifies coverage gaps in the generated test cases — scenarios or requirements from the source document that may not be adequately covered. Each gap entry includes: * **Gap description** — What requirement or scenario is missing coverage * **Details** — Expanded view with additional context **Actions:** | Action | Description | | ---------------------- | --------------------------------------------------- | | **View Details** | Open the gap detail drawer for full context | | **Add to Test Cases** | Generate a test case to cover this specific gap | | **Add All Test Cases** | Generate test cases for all identified gaps at once | ### Metadata tab Displays detailed information about the uploaded file: * File name, type, and size * Upload date and time * Uploaded by (team member name) * Processing status and duration * Associated workspace and project details ### History tab {% hint style="info" %} The history tab is coming soon. It will display a timeline of changes made to the uploaded file and its generated test cases. {% endhint %} *** ## Related documentation * [Creating Test Cases](/web-testing/creating-test-cases.md) — Import files using the creation dialog * [AI Test Generation](/ai-features/ai-test-generation.md) — All AI test generation methods * [Managing Test Suites](/web-testing/managing-test-suites.md) — Organize generated test cases into suites --- # 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://learning.contextqa.com/web-testing/uploaded-test-files.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.