Updates:
Status: Accepted
Labels: Target-2.8.2
Comment #3 on issue 1513 by pekka.klarck: Automatic variables is
unavailable in get_variables (or getVariables) method
http://code.google.com/p/robotframework/issues/detail?id=1513
Thanks to the provided example I both understood the problem better and was
able to reproduce it.
The problem is caused by changes to the test execution logic in 2.8.
Apparently ${SUITE SOURCE} variable is now set after imports when it was
done prior to them in previous releases. I looked at the code and it seems
that it's easy to change this so that this variable is set earlier.
What needs to be decided is how to handle suite related automatic variables
in general. Currently ${SUITE SOURCE}, ${SUITE NAME}, ${SUITE
DOCUMENTATION} and ${SUITE METADATA} are all set in same place after
imports. I guess the reason to do that after imports is that then all
variables in resource and variable files are imported, and possible
variables in ${SUITE DOCUMENTATION} and ${SUITE METADATA} can be resolved.
${SUITE SOURCE} and ${SUITE NAME} cannot contain variables so they could be
set prior to imports.
My current thinking is to set ${SUITE SOURCE} and ${SUITE NAME} prior to
imports and ${SUITE DOCUMENTATION} and ${SUITE METADATA} after them when
variables can be resolved. I want to verify how things worked in 2.7.7
before making the final decision, though.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "robotframework-commit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to robotframework-commit+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
