https://bugs.documentfoundation.org/show_bug.cgi?id=161803
Bug ID: 161803
Summary: UI tests: infrastructure for environment variables
Product: LibreOffice
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: framework
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: kolafl...@kolahilft.de
The ui tests may profit from a better infrastructure for setting environment
variables.
Currently there seem to be two possibilities to set environment variables
needed for UI tests. But I've heard arguments against both.
https://git.libreoffice.org/core/+/3c91fb758a429f51b89dfe9cea088691ced6d0c1/solenv/gbuild/UITest.mk#42
https://git.libreoffice.org/core/+/3c91fb758a429f51b89dfe9cea088691ced6d0c1/uitest/libreoffice/connection.py#95
To me those possibilities don't look ideal.
Please share your opinion. Do you think the existing possibilities are fine? Or
do you have in idea how this could be solved in a better way?
Here's an example UITest which needs to set the GNUPGHOME environment variable.
https://gerrit.libreoffice.org/c/core/+/167904
Here it's being done via solenv/gbuild/UITest.mk
https://gerrit.libreoffice.org/c/core/+/167904/4/solenv/gbuild/UITest.mk
And here it's being done via uitest/libreoffice/connection.py
https://gerrit.libreoffice.org/c/core/+/167904/3/uitest/libreoffice/connection.py
--
You are receiving this mail because:
You are the assignee for the bug.
