I have a test that opens Microsoft Teams using the following step:
Even with the use of the "--remote-debugging-port=8081" argument, I still cannot identify any of the elements within Teams, e.g. the navigation buttons, using Ranorex Spy.
Is there anything wrong with the step shown above? Is there anything else I can do, to create tests that work on Microsoft Teams?
Thanks
Identifying elements in Microsoft Teams?
-
- Certified Professional
- Posts: 455
- Joined: Tue Feb 18, 2014 2:14 pm
- Location: Co Louth, Ireland
- Contact:
Identifying elements in Microsoft Teams?
You do not have the required permissions to view the files attached to this post.
Re: Identifying elements in Microsoft Teams?
Hi,
Try using single dash instead of double dash in front of the command line -remote-debugging-port=8081. I believe that double dash is required only for Chrome/Edge browser?
Try using single dash instead of double dash in front of the command line -remote-debugging-port=8081. I believe that double dash is required only for Chrome/Edge browser?
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
-
- Certified Professional
- Posts: 455
- Joined: Tue Feb 18, 2014 2:14 pm
- Location: Co Louth, Ireland
- Contact:
Re: Identifying elements in Microsoft Teams?
Thank you very much odklizec, I've tried the argument with a single hyphen as shown below. The Teams app still opens but unfortunately I still cannot id elements in it with Spy.
Code: Select all
-remote-debugging-port=8081
-
- Certified Professional
- Posts: 455
- Joined: Tue Feb 18, 2014 2:14 pm
- Location: Co Louth, Ireland
- Contact:
Re: Identifying elements in Microsoft Teams?
This is how the Ranorex report looks after I run the module to open the Teams app.
You do not have the required permissions to view the files attached to this post.
Re: Identifying elements in Microsoft Teams?
Hi,
I'm afraid, I'm out of ideas then. Have you tried to implement --remote-debugging-port=8081 outside Ranorex studio project? I mean, try to add it to the Teams desktop shortcut.
I'm afraid, I'm out of ideas then. Have you tried to implement --remote-debugging-port=8081 outside Ranorex studio project? I mean, try to add it to the Teams desktop shortcut.
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
-
- Certified Professional
- Posts: 455
- Joined: Tue Feb 18, 2014 2:14 pm
- Location: Co Louth, Ireland
- Contact:
Re: Identifying elements in Microsoft Teams?
Thanks again for your help and suggestions odklizec, very much appreciated.
I added the argument to the Target in the Shortcut and also opened Teams via the command line with the argument added. Neither of those options enabled object identification within Teams, using Spy.
I added the argument to the Target in the Shortcut and also opened Teams via the command line with the argument added. Neither of those options enabled object identification within Teams, using Spy.
Re: Identifying elements in Microsoft Teams?
Hi,
I have same problem here with teams. Any suggestions to solve this issue?
kind regards, bmt
I have same problem here with teams. Any suggestions to solve this issue?
kind regards, bmt
