---
title: Test and debug Actors
url: https://docs.apify.com/actors/development/test-and-debug.md
parents:
  - [Apify documentation](https://docs.apify.com/llms.txt)
  - [Actors](https://docs.apify.com/actors.md)
  - [Develop](https://docs.apify.com/actors/development.md)
children:
  - [Debugging](https://docs.apify.com/actors/development/debugging.md)
previous: [Migration guide](https://docs.apify.com/actors/development/permissions/migration-guide.md)
next: [Debugging](https://docs.apify.com/actors/development/debugging.md)
---

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

# Test and debug Actors

An Actor that works on your machine can still fail on the Apify platform. Run your Actor locally while you develop, test it on the platform before you release it, and debug the runs that fail.

## Test locally

Before you deploy your Actor, run it locally with the [Apify CLI](https://docs.apify.com/cli/docs):


```bash
apify run
```


The run reads its input from `storage/key_value_stores/default/INPUT.json` and writes its output to the `storage` folder of your project. You can edit `INPUT.json` to try different inputs, and check the results without using platform resources.

## Test on the Apify platform

To catch problems that only appear in a real run, such as proxy errors or memory limits, use [apify-test-tools](https://github.com/apify/apify-test-tools). It's an open-source package that builds, tests, and releases Actors from a Git repository.

apify-test-tools has three parts:

* A Vitest library for writing tests that run your Actor on the Apify platform and check its status, log, dataset, and key-value store. It also supports [Server Actors](https://docs.apify.com/actors/development/programming-interface/server-actors.md).
* GitHub Actions workflows that build and test the Actors changed in each pull request, release them on every merge, and run tests on a schedule to catch problems caused by changes on target websites.
* A CLI for building your own pipeline on a CI platform other than GitHub, or for building and testing locally.

The tool builds and tests only the Actors that a change affects, which saves time and platform costs in repositories with many Actors.

For example, the following workflow builds and tests the changed Actors on every pull request:

.github/workflows/pr-build-devel-test.yaml


```yaml
name: PR test



on:

    pull_request:

        branches: [master]



jobs:

    buildDevelAndTest:

        uses: apify/apify-test-tools/.github/workflows/public_pr-build-test.yaml@workflows-v0

        secrets:

            CONFIG_SECRETS: |

                {

                    "APIFY_TOKEN_MYTEAM": "${{ secrets.APIFY_TOKEN_MYTEAM }}",

                    "APIFY_TOKEN_PARTNER": "${{ secrets.APIFY_TOKEN_PARTNER }}"

                }
```


For the full setup, including the workflows for releases and scheduled tests, see the [README](https://github.com/apify/apify-test-tools/blob/master/README.md).

## Debug Actor runs

You can reproduce most bugs locally with your IDE's debugger. When a bug only happens on the platform, attach a debugger to the run itself. You can set breakpoints and inspect variables from your browser or from your local IDE.

For details, see [Debug Actors on the Apify platform](https://docs.apify.com/actors/development/debugging.md).
