In my payment Win10 UI test(with a sandbox user for test payments) during purchasing procedure from the Store I check the product price text which should be "$0.00" to confirm that the purchase is a test one. See attachments.
Run with: WinAppDriver 1.0.9.0 , appium 1.6.5 beta.
There is issue with the text(element properties) caching on the driver side. When the test fetches the text element from "PriceContainer" group it is always "" (empty). But visually the text "$0.00" exists. See screenshot. Winappdriver`s findElement command returns the real text only if I investigate manually the field with 'inspect' tool from Windows 10 SDK. Suppose this action impacts on an internal driver cache update.
In my payment Win10 UI test(with a sandbox user for test payments) during purchasing procedure from the Store I check the product price text which should be "$0.00" to confirm that the purchase is a test one. See attachments. Run with: WinAppDriver 1.0.9.0 , appium 1.6.5 beta. There is issue with the text(element properties) caching on the driver side. When the test fetches the text element from "PriceContainer" group it is always "" (empty). But visually the text "$0.00" exists. See screenshot. Winappdriver`s findElement command returns the real text only if I investigate manually the field with 'inspect' tool from Windows 10 SDK. Suppose this action impacts on an internal driver cache update.
I tried to fetch the text element with different selector type by id and xpath without success.