Support @TEST-ENV #112
Description
In certain cases, it could be useful to set an environment variable for all TEST-EXEC / TEST-EXEC-FAIL commands.
Instead of repeating it on each line, I wonder if @TEST-ENV could be a useful keyword.
# @TEST-ENV: OPENSSL_ENABLE_SHA1_SIGNATURES=1
# @TEST-EXEC: zeek -b ...
# @TEST-EXEC: zeek -b ...
Thoughts? I wonder how often this comes up? Setting a custom canonifier for btest-diff is another case where I could see that useful.