Run changed tests before a PR

Task guide

Run the local tests Glade can connect to your branch diff, then save machine-readable output.

• Run changed tests against origin/main.
• Rerun failures.
• Write reports for review or CI.

For the main task path, use the guide. This walkthrough keeps the illustrated steps and recovery details for this interface.

The git examples assume origin/main is your intended base ref and is available locally. Substitute the correct existing ref for your repository before running changed-test or refactor commands.

Before you start

• Your branch has access to origin/main.
• reports/ exists before commands write files there.
• Run from the initialized Salesforce DX project root.

The screenshots for this article were captured in a terminal.

Steps

1. Run changed tests

glade test changed --project . --since origin/main --no-progress

Expected: Glade selects tests conservatively from the diff and prints a local summary. Read the executed count: zero selected tests may exit 0; run an explicit relevant class or suite when you need execution evidence.

2. Save review artifacts

mkdir -p reports
glade test changed --project . --since origin/main --json --no-progress > reports/glade-test-changed.json
glade test --project . --junit reports/glade-junit.xml --no-progress
wc -c reports/glade-test-changed.json reports/glade-junit.xml

Expected: reports/ contains JSON and JUnit output for PR review or CI upload.

Common wrong turn

The comparison ref must exist locally. Fetch it before running changed-test selection; in GitHub Actions, use fetch-depth: 0. Glade compares against the specified ref directly; it does not calculate a merge base.

Next

• Add Glade to CI
• Affected tests