Hi,
Has anyone seen issues with a default value getting ignored when selecting option in a DL?
Scenario
module variable 'varStateID' = default 99
element path for DL selector = .//select[@id='ctl00_ctl00_MainContent_ChildContent1_FrmCustIdentification_cboState']
action = Set value TagValue $varStateID element
During execution, the set value just skips right over the field.
I've used this approach many times to consistently select states in a DL...but in one form, in one case, I am relying initially on the default value until I have test data defined.
Thoughts?
Lorinda
variable default value not used in set value on droplist
Re: variable default value not used in set value on droplist
Hi,
Does this problem happen both if you run entire test suite and standalone recording module? Have you tried to set a breakpoint at failing line of code and debug it?
My guess is that it fails when you run entire test suite? Do you have any data connector connected to the module variable? In this case, data connector value has priority over default module variable.
Does this problem happen both if you run entire test suite and standalone recording module? Have you tried to set a breakpoint at failing line of code and debug it?
My guess is that it fails when you run entire test suite? Do you have any data connector connected to the module variable? In this case, data connector value has priority over default module variable.
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration
Re: variable default value not used in set value on droplist
Hi,
Have you checked this blog post?...
https://www.ranorex.com/blog/sharing-da ... o-another/
This article is exactly about sharing data between modules.
Have you checked this blog post?...
https://www.ranorex.com/blog/sharing-da ... o-another/
This article is exactly about sharing data between modules.
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration
Re: variable default value not used in set value on droplist
Thanks, Pavel. Yes, I have read the link you shared.
The issue was this "...in this case, data connector value has priority over default module variable."
That put me on the right track!
The issue was this "...in this case, data connector value has priority over default module variable."
That put me on the right track!
Re: variable default value not used in set value on droplist
Hi,
Good to hear you managed to track the source of issue!
Good to hear you managed to track the source of issue!
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration