<commit_before>---
layout: toc-top
title: Dashboard
containerClass: faq
---

## <Icon name="angle-right"></Icon> What is the Dashboard?

<DocsImage src="/img/dashboard/dashboard-runs-list.png" alt="Dashboard Screenshot" ></DocsImage>

The [Dashboard](https://on.cypress.io/dashboard) is a Cypress service that gives you access to tests you've recorded - typically when running Cypress tests from your [CI provider](/guides/continuous-integration/introduction). The Dashboard provides you insight into what happened during your tests run.

You can read more [here](/guides/dashboard/introduction).

## <Icon name="angle-right"></Icon> How do I record my tests?

1. First [set up the project to record](/guides/dashboard/projects#Setup).
2. Then [record your runs](/guides/dashboard/runs).

After recording your tests, you will see them in the [Dashboard](https://on.cypress.io/dashboard) and in the "Runs" tab of the Test Runner.

## <Icon name="angle-right"></Icon> How much does it cost?

Please see our [Pricing Page](https://www.cypress.io/pricing) for more details.

## <Icon name="angle-right"></Icon> What counts as a test result?

Which [pricing tier](https://www.cypress.io/pricing) is best for you depends on the number of test you record each month in your organization.

Tests are recorded when [cypress run](/guides/guides/command-line#cypress-run) is called with the `--record` flag while supplying the record `--key`. This means your [test run data](/guides/dashboard/runs) is being "recorded" to the Dashboard.

We consider each time the `it()` function is called to be a single test. So you will generally have several tests recorded within each spec file and likely several spec files within a single run.

You can always see how many tests you've recorded from your organization's [Billing & Usage](/guides/dashboard/organizations#Billing-amp-Usage) page within the Dashboard.

## <Icon name="angle-right"></Icon> What counts as a user?

A [user](/guides/dashboard/users) is anyone with a login to our Dashboard Service that has been invited to see and review the test results of your organization.

## <Icon name="angle-right"></Icon> What is the difference between public and private projects?

**A public project** means that anyone can see the recorded runs for it. It's similar to how public projects on Github, Travis, or Circle are handled. Anyone who knows your `projectId` will be able to see the recorded runs, screenshots, and videos for public projects.

**A private project** means that only [users](/guides/dashboard/users) you explicitly invite to your [organization](/guides/dashboard/organizations) can see its recorded runs. Even if someone knows your `projectId`, they will not have access to your runs unless you have invited them.

## <Icon name="angle-right"></Icon> How is this different than CI?

Cypress is **complementary** to your [CI provider](/guides/continuous-integration/introduction), and plays a completely different role.

It doesn't replace or change anything related to CI. You will run Cypress tests in your CI provider.

The difference between our [Dashboard Service](/guides/dashboard/introduction) and your CI provider is that your CI provider has no idea what is going on inside of the Cypress process. It's programmed to know whether or not a process failed - based on whether it had an exit code greater than `0`.

Our [Dashboard Service](/guides/dashboard/introduction) provides you with the low level details of _what_ happened during your run. Using both your CI provider + Cypress together gives the insight required to debug your test runs.

When a run happens and a test fails - instead of going and inspecting your CI provider's `stdout` output, you can log into the [Dashboard](https://on.cypress.io/dashboard), see the `stdout` as well as screenshots and video of the tests running. It should be instantly clear what the problem was.

## <Icon name="angle-right"></Icon> Can I host the Dashboard data myself?

No, although we are looking to build an on-premise version of the Dashboard for use in private clouds. If you're interested in our on-premise version, please add your interest to our [Dashboard Product Board](https://portal.productboard.com/cypress-io/1-cypress-dashboard)!
<commit_msg>update what counts as recorded tests (#3966)<commit_after>---
layout: toc-top
title: Dashboard
containerClass: faq
---

## <Icon name="angle-right"></Icon> What is the Dashboard?

<DocsImage src="/img/dashboard/dashboard-runs-list.png" alt="Dashboard Screenshot" ></DocsImage>

The [Dashboard](https://on.cypress.io/dashboard) is a Cypress service that gives you access to tests you've recorded - typically when running Cypress tests from your [CI provider](/guides/continuous-integration/introduction). The Dashboard provides you insight into what happened during your tests run.

You can read more [here](/guides/dashboard/introduction).

## <Icon name="angle-right"></Icon> How do I record my tests?

1. First [set up the project to record](/guides/dashboard/projects#Setup).
2. Then [record your runs](/guides/dashboard/runs).

After recording your tests, you will see them in the [Dashboard](https://on.cypress.io/dashboard) and in the "Runs" tab of the Test Runner.

## <Icon name="angle-right"></Icon> How much does it cost?

Please see our [Pricing Page](https://www.cypress.io/pricing) for more details.

## <Icon name="angle-right"></Icon> What counts as a test result?

Which [pricing tier](https://www.cypress.io/pricing) is best for you depends on the number of test you record each month in your organization.

Tests are recorded when [cypress run](/guides/guides/command-line#cypress-run) is called with the `--record` flag while supplying the record `--key`. This means your [test run data](/guides/dashboard/runs) is being "recorded" to the Dashboard.

We consider each time the `it()` function is called to be a single test. So you will generally have several tests recorded within each spec file and likely several spec files within a single run. Only the [passed and failed tests](/guides/core-concepts/writing-and-organizing-tests#Test-statuses) are counted. The pending and skipped tests are NOT counted.

You can always see how many tests you've recorded from your organization's [Billing & Usage](/guides/dashboard/organizations#Billing-Usage) page within the Dashboard.

## <Icon name="angle-right"></Icon> What counts as a user?

A [user](/guides/dashboard/users) is anyone with a login to our Dashboard Service that has been invited to see and review the test results of your organization.

## <Icon name="angle-right"></Icon> What is the difference between public and private projects?

**A public project** means that anyone can see the recorded runs for it. It's similar to how public projects on Github, Travis, or Circle are handled. Anyone who knows your `projectId` will be able to see the recorded runs, screenshots, and videos for public projects.

**A private project** means that only [users](/guides/dashboard/users) you explicitly invite to your [organization](/guides/dashboard/organizations) can see its recorded runs. Even if someone knows your `projectId`, they will not have access to your runs unless you have invited them.

## <Icon name="angle-right"></Icon> How is this different than CI?

Cypress is **complementary** to your [CI provider](/guides/continuous-integration/introduction), and plays a completely different role.

It doesn't replace or change anything related to CI. You will run Cypress tests in your CI provider.

The difference between our [Dashboard Service](/guides/dashboard/introduction) and your CI provider is that your CI provider has no idea what is going on inside of the Cypress process. It's programmed to know whether or not a process failed - based on whether it had an exit code greater than `0`.

Our [Dashboard Service](/guides/dashboard/introduction) provides you with the low level details of _what_ happened during your run. Using both your CI provider + Cypress together gives the insight required to debug your test runs.

When a run happens and a test fails - instead of going and inspecting your CI provider's `stdout` output, you can log into the [Dashboard](https://on.cypress.io/dashboard), see the `stdout` as well as screenshots and video of the tests running. It should be instantly clear what the problem was.

## <Icon name="angle-right"></Icon> Can I host the Dashboard data myself?

No, although we are looking to build an on-premise version of the Dashboard for use in private clouds. If you're interested in our on-premise version, please add your interest to our [Dashboard Product Board](https://portal.productboard.com/cypress-io/1-cypress-dashboard)!

{'fraction_non_alphanumeric': 0.0904609034625086, 'fraction_numerical': 0.001375831231368952, 'mean_word_length': 4.716251638269987, 'pattern_counts': {'":': 0, '<': 39, '<?xml version=': 0, '>': 39, 'https://': 12, 'lorem ipsum': 0, 'www.': 4, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3384100', 'n_tokens_mistral': 2339, 'n_tokens_neox': 2307, 'n_words': 1136}