Thank you for the provided information.
The behavior of the test is indeed unexpected and in order to provide additional guidance, I will need some further details from your side:
- Does the test fail during execution? If that is the case, can you please attach the step failure details for it? If the test does not fail, please attach the execution log. This way I will get a better overview of the test steps.
- Can you record a short video, of the test quick execution, with annotation turned on (step 5 in this article)? With it, I will be able to see what actions are executed, especially for the step that is misbehaving.
- It will be very helpful, if you can provide an example application for us to test with and reproduce the faulty behavior.
At this point, I can suggest that you try and remove the filter by id
and replace it with filter by the attribute src
with the exact value "/App_Themes/Orange/images/Icones/ExcelBlue.png
" or containing only "ExcelBlue.png"
. Such changes may fix the issue, but the step failure details/execution log should provide more details about the test execution. Alternatively, you can also try to use chained find expressions
to add additional filter to narrow the DOM to a parent element and apply the find element logic
to this element only and not the whole page.
Thank you for your cooperation and understanding.