> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/settings/organization/pull-request-data-quality/pull-request-test-file-rules.md).

# Test file rules

Classify changed files as code or test so you can track code and test changes separately in pull request metrics

In pull request settings, you can define [gitignore-style](https://git-scm.com/docs/gitignore) rules that classify changed files as test files. Files that do not match are classified as code.

Use test file rules when you want separate metrics for code changes and test changes — for example, to see how much production code changed compared to test updates in a pull request.

[Test file rules settings](https://app.swarmia.com/settings/pull-requests/test-file-rules)

## How rules work

* One pattern per line
* Paths are relative to the repository root
* Test file rules do not exclude files from pull request size calculations — use [file exclusion rules](/settings/organization/pull-request-data-quality.md) for that

## Default patterns

New organizations start with common test file patterns, such as `*.test.ts`, `__tests__/**`, and `*_test.go`. You can edit these rules to match how your repositories name test files.

## After you save

When you update test file rules, Swarmia recalculates file classifications for your pull requests. This may take a while for large organizations.


---

# 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://help.swarmia.com/settings/organization/pull-request-data-quality/pull-request-test-file-rules.md?ask=<question>&goal=<user_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.