# Requirements Library

The Requirements Library lets you manage uploaded requirement files and the test cases generated from them. After you import a requirements document through the [Create Test Case](/web-testing/creating-test-cases.md) dialog, the file appears in the library where you can track its processing status, review generated test cases, inspect AI analysis, identify coverage gaps, and view file metadata.

## Opening the requirements library

1. Select **Test Development** from the left sidebar.
2. Under the **Design & Development** section, click **Imported Files**.

The Requirements Library list view opens, showing all uploaded requirement files for the current workspace.

## Requirements list view

The list view displays a table of all uploaded files with the following columns:

| Column             | Description                               |
| ------------------ | ----------------------------------------- |
| **Id**             | Numeric identifier for the upload         |
| **Name**           | File name (click to open the detail view) |
| **Type**           | File format (e.g., EXCEL, CSV)            |
| **Status**         | Current processing status (see below)     |
| **Estimated Time** | Processing duration                       |
| **Test Cases**     | Number of generated test cases            |
| **Created by**     | Team member who uploaded the file         |
| **Created Date**   | Upload date and time                      |

### Status values

| Status                           | Meaning                                             |
| -------------------------------- | --------------------------------------------------- |
| **Completed**                    | Processing finished and test cases are available    |
| **Pending action**               | AI needs clarification before generating test cases |
| **Processing** / **In progress** | File is currently being analyzed                    |
| **Failed** / **Error**           | Processing encountered an error                     |

Use the search bar to filter files by name. The list supports server-side pagination and auto-refresh.

### Answering clarification questions

When a file has the **Pending action** status, click its name to open a clarification dialog. ContextQA's AI analyzed your requirements and needs additional context before generating test cases.

The dialog displays:

* The AI's analysis message explaining what it understood
* A list of clarification questions with text fields for your answers

You can either answer the questions and click **Submit**, or click **Skip & Generate Test Cases** to proceed without providing additional context.

***

## Requirement detail view

Click any file name in the list to open its detail view. The header displays:

* **File name** and **status badge**
* **Metadata row** — file type, test type (Web or Mobile), requirement code, creator name, and creation date
* **Generated test cases count**
* **Filter badges** — filter test cases by type (Positive, Negative, Edge, etc.) and status (Approved, Rejected, Pending)
* **Export** button — download the requirement data
* **Back** button — return to the library list

The detail view contains six tabs:

* [Test Cases](#test-cases-tab)
* [Questionnaire](#questionnaire-tab)
* [AI Analysis](#ai-analysis-tab)
* [Gaps](#gaps-tab)
* [Metadata](#metadata-tab)
* History (coming soon)

***

## Test cases tab

The default tab displays all test cases generated from the uploaded requirement file in a searchable, filterable table.

### Searching and filtering

Use the search bar at the top to find test cases by name. Click the **filter** button to open the filter panel and narrow results by status, type, or other criteria. Active filters appear as removable chips above the table.

### Reviewing a test case

Click any test case row to open the **test case detail drawer** on the right side of the screen. The drawer shows:

| Field            | Description                                        |
| ---------------- | -------------------------------------------------- |
| **Status badge** | Current status (e.g., Pending, Approved, Rejected) |
| **Case ID**      | Unique test case identifier                        |
| **Type badge**   | Test case type (Positive, Negative, Edge, etc.)    |
| **Title**        | Test case name                                     |
| **Description**  | Detailed description of the test scenario          |
| **Test Type**    | Classification of the test                         |
| **Variables**    | Variables used in the test steps                   |
| **Steps**        | Ordered list of test steps with expected results   |

### Approving or rejecting test cases

From the test case detail drawer, you can:

1. Click **Approve & Move to Repository** to accept the test case and add it to your test case repository.
2. Click **Reject** to decline the test case.
3. Click **Edit test case** to modify the title, description, test type, or steps before making a decision.

When editing, click **Save Changes** to keep your modifications or **Cancel Changes** to discard them. A confirmation dialog appears if you attempt to close the drawer with unsaved changes.

***

## Questionnaire tab

The Questionnaire tab displays the clarification questions that ContextQA's AI generated during requirement analysis, along with any answers you provided.

Each item shows the question text and an answer field. If no questions were generated, an empty state message appears.

***

## AI analysis tab

The AI Analysis tab provides a detailed breakdown of how ContextQA's AI interpreted your requirements document. The tab displays four information cards:

### AI understanding

A summary of what the AI understood from your requirements document. This appears as a highlighted section at the top of the tab.

### Assumptions made

A numbered list of assumptions the AI made during analysis. Review these to verify the AI correctly interpreted ambiguous or incomplete requirements.

### Coverage notes

A summary of which areas the generated test cases cover, with a bullet list of specific coverage points. Use this to verify that all critical requirements have corresponding test cases.

### Warnings and gaps

A list of potential issues the AI identified, such as:

* Requirements that could not be fully covered
* Ambiguous specifications that may need clarification
* Areas where additional test cases might be needed

### Confidence score

A progress bar showing how confident the AI is in its analysis (0–100%). A higher score indicates the requirements were clear and well-structured. The score includes a descriptive label explaining the confidence level.

***

## Gaps tab

The Gaps tab identifies areas where your requirements may not be fully covered by the generated test cases. Gaps appear as cards in a two-column grid layout.

### Gap cards

Each gap card displays:

* **Title** — what the gap is about
* **Similarity score** — a progress bar showing how closely existing test cases match this requirement area (lower scores indicate larger coverage gaps)
* **Tags** — requirement ID, test case priority, test case type, and prerequisite warnings
* **Why missing** — explanation of why this gap exists
* **View details** — opens the gap detail drawer

### Gap detail drawer

Click **View details** on any gap card to open a side panel with:

| Section                     | Description                                                                                      |
| --------------------------- | ------------------------------------------------------------------------------------------------ |
| **Similarity score**        | A ring chart showing the similarity percentage with a descriptive explanation                    |
| **Summary**                 | Detailed summary of the coverage gap                                                             |
| **What's missing**          | Numbered list of specific items not covered by existing test cases                               |
| **AI-suggested test cases** | Test cases the AI recommends to fill the gap, each with a confidence percentage and status badge |

### Adding suggested test cases

From the gap detail drawer:

* Click **Add to Test Cases** on an individual suggestion to add it to your test case repository.
* Click **Add All** in the footer to add all pending suggestions at once.

Suggestions that have already been added display an "Already Added" badge with the linked test case ID.

To dismiss a gap you do not need to address, click **Close** to return to the gap list.

***

## Metadata tab

The Metadata tab displays detailed information about the uploaded file, organized into four sections:

### File information

| Field          | Description                     |
| -------------- | ------------------------------- |
| **File Type**  | Format of the uploaded file     |
| **File Size**  | Size of the uploaded file       |
| **Page Count** | Number of pages in the document |
| **Word Count** | Total word count                |
| **Version**    | Document version                |

### Configurations

| Field                            | Description                                      |
| -------------------------------- | ------------------------------------------------ |
| **Test Plan**                    | Associated test plan (if created during import)  |
| **Test Suite**                   | Associated test suite (if created during import) |
| **Platform**                     | Target platform (Web or Mobile)                  |
| **Browser** or **Mobile Device** | Target browser or device (depends on platform)   |

### Timestamps

| Field             | Description                       |
| ----------------- | --------------------------------- |
| **Created By**    | Team member who uploaded the file |
| **Created At**    | Upload date and time              |
| **Last Modified** | Most recent modification date     |

### Labels

Displays any labels or tags associated with the requirement file. Click **+N** to expand and view all labels when more than five are assigned.

***

## Related documentation

* [Creating Test Cases](/web-testing/creating-test-cases.md) — How to import files and generate test cases
* [AI Test Generation](/ai-features/ai-test-generation.md) — All AI-powered test generation methods
* [Managing Test Suites](/web-testing/managing-test-suites.md) — Organize test cases into suites
* [Test Data Management](/web-testing/test-data-management.md) — Variables and data-driven testing


---

# 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/requirements-library.md?ask=<question>
```

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.