You can now use the standard
process.env.VARIABLE notation to read variables in all scripts. We already supported that for Browser check scripts, but not in setup & teardown scripts for API checks.
environment object still works, but we advise to use
process.env from now on. A short example.
Earlier you needed to read any variables from the proprietary / non-standard
environment object, e.g.
// a setup or teardown script const key = environment.API_KEY
Now you can just do
// a setup or teardown script const key = process.env.API_KEY
This should help with local debugging!