The Vercel integration automatically tests Vercel deployments, as well as tracking the performance and Lighthouse scores of your production site over time.
DebugBear will crawl your site and try to automatically set up monitoring for up to 3 pages. You can add customize these pages or add additional ones.
Go to the Vercel website to read the full guide on setting up performance testing for your Vercel project.
When you push a commit, DebugBear will compare it to the latest build on the master branch.
By default the build status will be neutral, but you can get pass/fail statuses by setting up performance budgets.
(Side note: expect your SEO score on the branch to be lower, as the preview build is blocked from indexing.)
If you install the GitHub integration the build statuses will also be added to your GitHub pull requests.
By default, each time you deploy your site pages in your project with URLs matching
project-name*.vercel.app will be tested. However, you might want to exclude some sites, or use a custom deployment suffix. The URL filter setting allows you do that.
By default, every Vercel deployment in your project will be tested. This can result in a large number of tests being run, and you might want restrict testing to deployments on certain branches.
You can do this by specifying one or more branch names in the Branch Filter setting. Separate branch names with spaces, for example
staging dev prod.
If you use Vercel's password protection feature you can set up a login flow to fill out the password before testing the page.
If you production deployment is not password protected, but your branch deployments aren't, then please get in touch and we can set up access.