> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fetchhive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Testing a Knowledge Base

> Run test searches, inspect matching chunks, and tune search settings before using a knowledge base

Use **Test Search** to check how a knowledge base responds before you connect it to a workflow or agent.

## Overview

The knowledge base detail page includes a **Test Search** action in the header. It opens a side sheet where you can enter a query, override search settings, and review the chunks that match your query.

Test searches use the selected knowledge base. They do not create or change knowledge base items, but they do create search activity that appears in knowledge base analytics and search records.

## How do I run a test search? <a href="#run-test-search" id="run-test-search" />

1. Open **Knowledge Bases** from the sidebar.
2. Open the knowledge base you want to test.
3. Click **Test Search** in the header.

4) Enter a **Search Query**.
5) Choose a **Search Type**.
6) Set **Chunk Limit**.
7) Set **Score Threshold**.
8) Click **Run**.

Fetch Hive shows matching chunks in the sheet after the search completes.

## How do I read test results? <a href="#read-test-results" id="read-test-results" />

Each result card shows the returned chunk content and a match score. Higher scores mean the chunk is a stronger match for the query.

Use the collapse action on a result card when you want to scan results quickly.

If no results appear, try a broader query, lower **Score Threshold**, or increase **Chunk Limit**.

If results are too broad, raise **Score Threshold** or switch **Search Type**. **Hybrid** is the recommended starting point. **Vector** is useful for conceptual matches. **Full Text** is useful for exact words or phrases.

## How do I tune search settings? <a href="#tune-search-settings" id="tune-search-settings" />

Start with the knowledge base defaults:

* **Search Type** set to **Hybrid**
* **Chunk Limit** set to 5
* **Score Threshold** set to your knowledge base default

Run a few realistic queries. Review whether the returned chunks contain enough context for the workflow or agent that will use them.

Increase **Chunk Limit** when answers need more source context. Raise **Score Threshold** when too many weak matches appear. Lower **Score Threshold** when relevant chunks are missing.

After you find a better default, edit the knowledge base settings from the knowledge base detail page.

## Where do test searches show up? <a href="#test-search-records" id="test-search-records" />

Test searches are stored as knowledge base search activity. The detail page analytics update after test searches run, including total searches and average search duration for the selected date range.

Use [Logs](./logs) for processing runs such as custom text, document upload, and website scrape activity. Use the knowledge base detail analytics when you want a quick view of search volume and search duration.

See also: [Search Knowledge Base](../workflows/steps/knowledge-base/search-knowledge-base) and [Vector Search](../agents/mcp-tools/vector-search)