How to run tests automatically in Replit

Before automating, confirm your tests work when run manually from Shell. Open Shell (Tools > Shell) and run your test command: 'npm test' for Node.js or 'pytest' for Python. All tests should pass. If any tests fail, fix them first since automating broken tests will block your workflow. Note the exact command that runs your tests because you will use it in automation scripts.

1# For Node.js projects:
2npm test
3
4# For Python projects:
5pytest -v
6
7# If no test script exists in package.json, add one first:
8# "scripts": { "test": "jest --verbose --forceExit" }

The simplest form of test automation is running tests every time you press the Run button. Open your .replit file (enable 'Show hidden files' in the file tree menu) and modify the run command to execute tests before starting the application. Use the && operator so the app only starts if all tests pass. If any test fails, the run stops and you see the failure output in the Console without the app starting.

1# .replit - Run tests before starting the app
2entrypoint = "index.js"
3run = "npm test && node index.js"

A Git pre-push hook runs your test suite before every push to GitHub. If tests fail, the push is blocked, preventing broken code from reaching the remote repository. Create a pre-push hook file in the .git/hooks directory from Shell. This is a standard Git feature that works in Replit's Shell environment. The hook runs automatically whenever you push via Shell or the Git pane.

1# Create the pre-push hook
2mkdir -p .git/hooks
3cat > .git/hooks/pre-push << 'HOOK'
4#!/bin/sh
5echo "Running tests before push..."
6npm test
7if [ $? -ne 0 ]; then
8  echo "Tests failed. Push blocked. Fix the failing tests and try again."
9  exit 1
10fi
11echo "All tests passed. Pushing..."
12HOOK
13chmod +x .git/hooks/pre-push

Add your test command to the deployment build step in .replit so tests must pass before code can be deployed to production. This is the most critical automation point since it prevents untested code from reaching users. Open .replit and modify the [deployment] build command to include your test step before the build step. RapidDev recommends this as a mandatory practice for any production application.

1[deployment]
2run = ["sh", "-c", "node index.js"]
3build = ["sh", "-c", "npm install && npm test && npm run build"]
4deploymentTarget = "cloudrun"

During active development, run tests in watch mode so they automatically re-execute whenever you save a file. Open a second Shell tab (or split the Shell pane) and run your test framework in watch mode. Jest has built-in watch mode; pytest can use the pytest-watch plugin. This gives you instant feedback on whether your changes break existing tests, without manually running the test command each time.

1# Jest watch mode (Node.js):
2npx jest --watch
3
4# For pytest, install pytest-watch first:
5pip install pytest-watch
6ptw -- -v

Combine test execution with Git operations in a single Shell script. Create a script that runs tests, and only if they pass, stages all changes, commits with a message, and pushes to GitHub. This workflow ensures every commit in your Git history has passing tests. Save the script in your project and run it from Shell whenever you are ready to commit.

1#!/bin/bash
2# scripts/commit.sh - Test, commit, and push in one step
3
4echo "Running test suite..."
5npm test
6
7if [ $? -ne 0 ]; then
8  echo "Tests failed. Commit aborted."
9  echo "Fix the failing tests and try again."
10  exit 1
11fi
12
13echo "All tests passed."
14echo "Staging and committing changes..."
15
16git add .
17git commit -m "$1"
18
19if [ -z "$1" ]; then
20  echo "No commit message provided. Usage: bash scripts/commit.sh 'Your message'"
21  exit 1
22fi
23
24git push origin main
25echo "Changes committed and pushed successfully."