Variables passing bug
See original GitHub issueHello, @fhoeben ,
Looks like there is a bug, that you cant access variables created in SuiteSetUp’s and other test pages by ‘EchoFixture’ in ‘JsonFixture’ for validation values. Attaching screenshot:
Variable created in SuiteSetUp
Variable created in previous test page:
Additional information:
- Variables are not accessible only for validation values (as shown in screenshot).
- Variables are accessible if they are created in SetUp, or same test page.
- HsacFixtures version 4.15.2
- Fitnesse version 20200501
Workaround:
Call vars by EchoFixture on same test page, and recreate them… 😃
|script|echo fixture| |$variable=|echo|$variable|
Please don’t hesitate and ask if anything more is required, Julius
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Can't pass variables to dynamic pipelines due to a bug either ...
Passing variables should work i.e. in this case the `UPLOAD_TO_S3' variable should be present in target pipeline environment. GitLab version.
Read more >[BUG] <USER> and <PASS> variables not working #172
Describe the bug When trying to parse or they aren't parsed To Reproduce Steps to reproduce the behavior: Go to stacker for stacker...
Read more >Bug passing variables by reference - Stack Overflow
I have a rather simple issue. I wrote a computer code in C language that gets a graph in the form of an...
Read more >Bug? I cant pass variables from a sub report
hi all ! I have 2 variables that I want to pass from a sub report to the main one. But when I...
Read more >Bug with Global Variables in 5.9.0 - Katalon Community
Bug with Global Variables in 5.9.0 ... correct value (with it seemingly just passing the actual variable name, not the variable's value).
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve once tried to start fixing this, but it requires changes to the slim protocol. That;s where I decided it was not worth the hassle. When we really need variable values from suiteSetUp in a test, we just use the workaround (the backtick expressions will also work, if you use
$`variable`
(note the backtick starting after the $). In most cases though, it’s also possible to move some variable setting to setup or a collapsed include in a test template.A nice ‘feature’ resluting from this anomaly is that it can be used to hide sensitive information from test reports. I have a habit of setting stuff like credential information from suiteSetup, so that they don’t show up in the HTML reports
I agree it looks like a bug (and probably is). The reason is that a setup is executed as part of a test case, whereas suite setup is executed as a separate test case. One could argue that bleeding symbol values from one test to another is unexpected as well.