New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with $$.env variables in utilities #347

Closed
ntiss opened this Issue Nov 30, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@ntiss
Copy link

ntiss commented Nov 30, 2018

$$.env variables that are populated inside utilities, within a script $$.env.set(), are not shared (or returned) with the caller scenario.
When a utilities scenario is called by reference, the $$.env vars stay empty in the main scenario even if they are well fed in the script step (visible in the ca.pture tab).
However, it works fine with $.ctx variables.

Please find in attachment a simple scenario to reproduce and analyse : the $$.env.envRandomIdFromUtil is lost when running the third step of the main scenario.
In the same time $.ctx.ctxRandomIdFromUtil is well propagated

bug_envVarsInUtilities.scenarios.json.txt

@tbarn

This comment has been minimized.

Copy link
Member

tbarn commented Nov 30, 2018

@ntiss thanks for reporting this! I will take a look into it. How much of a blocker is this for you? I can get it added to the current sprint, but it will be a couple of weeks before the fix would be released.

@ntiss

This comment has been minimized.

Copy link
Author

ntiss commented Nov 30, 2018

Hi @tbarn
This is not blocking at all for us since we can work through $.ctx vars.
I opened this issue because it's really weird and inconsistent between $.ctx and $$.env.

@lottamus

This comment has been minimized.

Copy link
Member

lottamus commented Dec 21, 2018

This issue has been fixed in v4.7.0. Thanks for reporting!

@lottamus lottamus closed this Dec 21, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment