> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/dashboard/analytics/run-size.md).

# Run Size

Track maximum specs and tests per run

Represents the **maximum** daily/weekly amount of specs/tests for fully completed runs. A fully reported run is a run that wasn't cancelled and didn't time out.

## Metrics

* **Spec files**: the **maximum** number of spec files detected in a run for the selected period
* **Tests**: the **maximum** number of tests detected in a run for the selected period
* **Trendline:** it can be configured as either a **linear trendline** or a **moving average** for maximum number of tests and maximum number of spec files.

{% hint style="info" %}
Cancelled or timed-out runs are excluded from the report.
{% endhint %}

<div data-with-frame="true"><figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2FxYV9YXUjyjYBA2QWCUAK%2FScreenshot%202026-09-22%20at%2010.36.14.png?alt=media&amp;token=88654c16-eb54-48d2-9068-7c1e80c0f912" alt=""><figcaption><p>Example chart - Run Size</p></figcaption></figure></div>

## Related

* [Suite Size](/dashboard/analytics/suite-size.md) - Track unique tests across all runs over time
* [Test Results](/dashboard/analytics/test-results.md) - Test outcome distribution
* [Analytics](/dashboard/analytics.md) - Analytics overview


---

# 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://docs.currents.dev/dashboard/analytics/run-size.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.