TestEnvironment erases all env variables
If TestEnvironment
is set, then instead of inheriting the current environment, only this environment is set. For example, adding TestEnvironment=GLIB_TEST_COMPILATION=1
to the .test
file will empty any PATH
that might be set before the environment.
TestEnvironment
should complement the existing one. See the g_subprocess_launcher_set_environ()
call which says:
Typically you will build this variable by using g_listenv() to copy the process 'environ' and using the functions g_environ_setenv(), g_environ_unsetenv(), etc.