How do I test in production without having to recommit?

[adamjabarry]

Summary

Hi,
I am new(ish) to Vercel and I have just deployed my application to GitHub and then to Vercel. While it is working locally, it is unfortunately not working when I deploy it (I think there is an issue with a call to an API or something). How do I go about running tests (console logs in my javascript, etc) to figure out what the issue is? I don't want to have to contiuously make amendments to my local code, push it to GitHub, and then wait for it to deploy. I feel like that would be super time consuming and would also clog up my GitHub commits. How do people usually go about testing in this environment. Any help would be greatly appreciated. Thank you!

Example

No response

Steps to Reproduce

This is more of a conceptual problem rather than an individual code problem. I am sure I will have another issue in production but not in development and I would like to figure out how to take the steps to tackled it. Thanks!

[amyegan]

Hey @adamjabarry! I usually use Vercel CLI to check builds on my local computer.

The vercel dev command is useful for running a development build, and vercel build can be used to make sure a build will succeed.

If the problem is caused by a missing environment variable, you can review them in project settings or use the CLI to pull variables into a local file and check that they match what you expect.

You can also deploying projects from Vercel CLI if you want to deploy without pushing test code to GitHub.

[adamjabarry]

Hi Amy,

Thank you so much for your response. It has been super helpful!

Best,
Adam

[github-actions[bot]]

This discussion was automatically locked because the community moved to a new site. Please join us at vercel.community