Improvement
You can now access the environment name and deployment ID in your checks when triggered by a deployment. It joins the already available environment url
You can use this info in your browser check scripts and/or setup & teardown scripts to make decisions on what environment you want to test against.
You access these variables with the familiar notation
process.env.ENVIRONMENT_NAME
newprocess.env.DEPLOYMENT_ID
newprocess.env.ENVIRONMENT_URL
These environment variables are populated based on the trigger provider. For example, when our Vercel integration triggers a check run on a preview, you will the following:
ENVIRONMENT_NAME
=preview
DEPLOYMENT_ID
=dpl_5fxyip1PaNvgoTF67SUnaMPyZFnv
ENVIRONMENT_URL
=https://webfrontend-fz9zq89zm-acme.vercel.app