Fix Set Header Values & Consolidate SeleniumExtentions Wait Methods#747
Conversation
…the Field Container
…xtended to Lookups & OptionSets + Refactor&Consolidate SeleniumExtensions
|
@AngelRodriguez8008 ,
|
|
Hi @KhoaAN, I found the bug, fixed it & add two tests for this sub-menu. What you mention is true the AppElementReference is not fully updated. How did you find this error? I couldn't find any associated test. Thanks for the review. |
Hi @AngelRodriguez8008 , |
|
Hi @AngelRodriguez8008 - It looks like this issue #747 and #749 have conflicts due to merging of one of the earlier PRs. Could you take a quick look and resolve those? Thanks, |
|
Yes, I implement these PRs independently, I will merge it now. Thanks! |
# Conflicts: # Microsoft.Dynamics365.UIAutomation.Api.UCI/WebClient.cs # Microsoft.Dynamics365.UIAutomation.Browser/Extensions/SeleniumExtensions.cs # Microsoft.Dynamics365.UIAutomation.Sample/UCI/Create/CreateActivity.cs
|
Hi @TYLEROL, I have a merge Issue hier. I add one required commit to this branch after you merge it, this is a Mayor Issue, Login was not working. Now i am getting problem with the fix #746 (by @rswafford) OpenRecord is not working in some cases. I will try to fix it. Sorry. BR |



Type of change
Description
When a tests is trying to set or get a field value, it was ignored in which context the field was. Header or Entity the container was the same. Repeated fields, in fields & form body, are not setting correctly. Also can be a problem in BPF, Quick Forms etc.
With new this approach field controls will be search in the desired context.
See bug #719 .
SeleniumExtentions (Wait Methods) are consolidated same signatures & logic for WaitUntil (Available, Visible, Clickable).
Fix also bug introduced in #707 see comment
Issues addressed
#719
#707
All submissions:
Which browsers was this tested on?