Describe the bug
We have placed the .robot.toml within our local user home directory (~/.robot.toml) but robotcode does not recognize this file at all which leads to missing variables in our test execution.
But somehow robotcode is unexpectedly recognizing and using a .robot.toml which is located under '/Users//Library/Application Support/robotcode/robot.toml'.
Within the .robot.toml file we are defining env variables via [extend-env] section.
Steps To Reproduce
Steps to reproduce the behavior:
- Place
.robot.tomlwithin home dir (~/.robot.toml)
- Define some env variables via
[extend-env] section
- execute test via VS Code
If possible add some example source code like:
Expected behavior
RobotCode is using the configuration file at ~/.robot.toml and extends the env variables during the test execution.
Screenshots/ Videos
Logs
I have observed the following log output from robotcode:
Use root at:
/Users/<my-user-dir>/development/gitrepos/<our-project> (.git directory)
Using config file: test/robot.toml
Found user configuration file:
/Users/<my-user-dir>/Library/Application Support/robotcode/robot.toml
Load configuration from /Users/<my-user-dir>/Library/Application Support/robotcode/robot.toml
Load configuration from test/robot.toml
Additional context
We are using an additional project specific configuration file within our git repo located in test/robot.toml - we would expect that robotcode is considering both config files and combines both content
Desktop (please complete the following information):
- VS Code Version 1.127.0
- RobotCode Version 2.5.1 and 2.7.0
- OS: MacOS
- Python Version 3.12.13
- RobotFramework Version RF-7.4.2
Describe the bug
We have placed the
.robot.tomlwithin our local user home directory (~/.robot.toml) but robotcode does not recognize this file at all which leads to missing variables in our test execution.But somehow robotcode is unexpectedly recognizing and using a
.robot.tomlwhich is located under '/Users//Library/Application Support/robotcode/robot.toml'.Within the
.robot.tomlfile we are defining env variables via[extend-env]section.Steps To Reproduce
Steps to reproduce the behavior:
.robot.tomlwithin home dir (~/.robot.toml)[extend-env]sectionIf possible add some example source code like:
Expected behavior
RobotCode is using the configuration file at
~/.robot.tomland extends the env variables during the test execution.Screenshots/ Videos
Logs
I have observed the following log output from robotcode:
Use root at: /Users/<my-user-dir>/development/gitrepos/<our-project> (.git directory) Using config file: test/robot.toml Found user configuration file: /Users/<my-user-dir>/Library/Application Support/robotcode/robot.toml Load configuration from /Users/<my-user-dir>/Library/Application Support/robotcode/robot.toml Load configuration from test/robot.tomlAdditional context
We are using an additional project specific configuration file within our git repo located in
test/robot.toml- we would expect that robotcode is considering both config files and combines both contentDesktop (please complete the following information):