Forum Discussion
Hi,
Is it possible to contact this development team and talk with them about the problem?
There is a chance that problematic control is some custom descendant from standard one with not all required inheritance been implemented.
Alternatively, if problematic control is inherited indeed, developers might provide you with the necessary information for proper control mapping in TestComplete https://support.smartbear.com/testcomplete/docs/working-with/managing-projects/properties/object-mapping.html.
Hi Alex,
With our current app, I know that a higher level of librairies are redefined for our app. Something like the "io" librairie containing pretty much all object types (checkboxes, droplists...). With TestComplete I could extend Androids checkbox with a descendant of it, but ours were redified at an higher level.
That being mentionned, I can spy the objects all the way down to the required buttons and controls. I can see the avaible methods and "Touch" is one of them, but it does not respond.
I am trying to get internal authorization to send our app to support or maybe have a small build containing juste enough code to reproduce the issue. Our app requires a dev server which is not available from outside our offices.
Thanks
- AlexKaras3 years agoChampion Level 3
Hi,
> or maybe have a small build containing juste enough code to reproduce the issue.
This is a good idea. Maybe developers will be able to create just a very simple standalone demo application that uses one or two problematic controls and can be used to reproduce the problem. So you may not need authorization to send this demo application to Support.
Additionally, I know that formal NDA sign-up could be considered with SmartBear's Support. You may discuss this with your management as well.
- sonya_m3 years agoSmartBear Alumni (Retired)
Thank you Alex, you've been extremely helpful!
slecault , did you manage to solve this? Please share your solution with us!
- slecault3 years agoContributor
Hi Sonya,
I am still waiting for internal authorization to U/L my app for diagnostic. The issue is still in place. The app development is done externally. If I had the code, I could probably supply a mini version to reproduce the issue.
At this time, I unfortunatly don't have a time frame yet.
I will do my best to get back to this post with more info in regards to cause/fix.
Thanks
Related Content
- 2 years agoFrits
- 4 years agoResearcher
- 3 years agoStephenWoolhead