Test Every AWS Amplify Preview Before It Merges
Seamlessly Integrates With Your Favorite AI-Powered Editors
No Workflow File
TestSprite installs as a GitHub App and only reads events, so it sits alongside your AWS Amplify pipeline rather than inside it. Nothing is added to .github/ and your existing workflows are untouched.
A URL Pattern, Not a Scraper
Amplify pull request previews are addressed by pull request number, so {pr} is normally the placeholder you want, with your app id kept literal in the pattern. Placeholders resolve per run: {pr}, {branch}, {branch-slug}, {sha}, and {short-sha} — so https://pr-123.d1a2b3c4.amplifyapp.com becomes https://pr-{pr}.{app-id}.amplifyapp.com.
Verify Before You Save
Send Test Event runs the whole flow against a sample pull request exactly like a real trigger. A comment appears in about 30 seconds — open the URL in it and confirm it is the environment you expect before creating the trigger.
A Fix Prompt, Not Just a Red Mark
Each failure expands to show what was expected, what was observed, a screenshot from the moment it broke, and a suggested fix prompt written to be pasted straight into your AI coding agent.
Catch It on the Preview, Not in Production
A preview deployment is the last place a regression is cheap to fix. Turn on Block PR until tests pass and the check becomes required, so a broken flow stops the merge rather than shipping and being found by a user.
Built for Teams Shipping on AWS Amplify
Pull Request or Branch
A pull request trigger tests each preview and comments on the PR. A push trigger tests a shared staging or production environment after every merge and posts a commit check. Both can run at once.
Web UI and APIs Together
Real browser flows against the deployed preview, plus backend API contract tests. Group them into a test list and one gate covers the whole deployment.
Or Drive It From the CLI
The open-source CLI does the same job from any CI system — free to install, Apache-2.0, and it needs only an API key in the environment.
Free Community Version
Offers a free community version, making us accessible to everyone.
Trusted By Businesses Worldwide
"Good job! Pretty cool MCP from TestSprite team! AI coding + AI testing helps you build better software easily!"
"TestSprite offers rich test case generation, clear structure, and easy-to-read code. It also supports simple online debugging with the ability to quickly expand by generating new test cases."
"TestSprite's automation helps us reduce tons of manual work. The developers can easily catch and resolve bugs earlier in the development process."
FAQ
Do I need to add a workflow file?
No. The integration is configured entirely in TestSprite and requires no changes to your repository. It listens to the deployment events AWS Amplify already reports.
How does TestSprite find the AWS Amplify preview URL?
You give it a URL pattern once. Amplify pull request previews are addressed by pull request number, so {pr} is normally the placeholder you want, with your app id kept literal in the pattern. Match the pattern against a real preview URL character by character, then use Send Test Event to confirm it resolves correctly before saving.
What if the preview URL has an unpredictable hash in it?
The pattern field expects something predictable. If your host generates random subdomains with nothing stable in them, configure an alias URL for the preview environment and point the pattern at that instead.
Amplify posts a bot comment with the preview link. Is that the event to use?
Often, yes — it is a reliable signal that the deployment finished and the URL is reachable. Use Detect Events on a recent pull request, pick that event, then send a test event to confirm the resolved URL actually loads before saving the trigger.
What does TestSprite actually test?
Web application UI in a real cloud browser, and backend APIs. It does not drive native iOS or Android UI, desktop applications, or emulators.
Is it free?
The open-source CLI is free to install and Apache-2.0 licensed, and there is a free community tier. Test execution runs in the cloud and consumes workspace credits — 0.5 per frontend run, 0.2 per backend run.