You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
I had troubles running unit tests across different environments and it turns out it's because the path to the ktr in the unit test xml is hardcode, even if I use ${UNIT_TESTS_BASE_PATH} via the setup dialog. If I define ${UNIT_TESTS_BASE_PATH}, I want this to be written to the xml file - unless I am doing something wrong here and there is already a better way in place.
As a workaround I currently edit the XML file manually and change the absolute path to a relative one.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I had troubles running unit tests across different environments and it turns out it's because the path to the ktr in the unit test xml is hardcode, even if I use
${UNIT_TESTS_BASE_PATH}
via the setup dialog. If I define${UNIT_TESTS_BASE_PATH}
, I want this to be written to the xml file - unless I am doing something wrong here and there is already a better way in place.As a workaround I currently edit the XML file manually and change the absolute path to a relative one.
The text was updated successfully, but these errors were encountered: