React Native support! (revived topic) *super important feature for mobile automation*

[TMbet]

ReactNative is a standard for mobile app development these days and TestComplete still doesn't support that. There exist some discussions in this forum that TesComplete might be support ReactNative but this is not true... I was discussing with TestComplete and they said that this is not possible. 
If TestComplete wants to be a competitive tool in mobile testing then ReactNative support is a must-have feature.
Sadly but this is a huge obstacle for our company and we even thinking about switching to another testing tool... 
Other well known commercial testing frameworks support this but TestComplete is not.
I strongly believe in this automation tool and I hope that Mobile Automation is the thing that you're planning to improve. Because it has always been a weak spot for TestComplete. 

[cunderw]

There isn't any special support like they say because there doesn't have to be. They still get converted to native objects when the app is ejected. I am not sure why they mentioned the tool cannot work with them. 

I just downloaded the apk here: https://github.com/invertase/react-native-material-design-demo and I am able to see the objects no problem. See attached screenshot (hopefully not blurry).

[TMbet]

@cunderw  that's true. This apk works for me too but with my apk I able to see only my Device 😞 
But it works with other testing frameworks...

[cunderw]

Have you tried having your devs eject the build and compile it with the PatchServices.jar? 

[TMbet]

@cunderw  when you say "eject the build" what do you specifically mean? Can you explain with more details, please 🙂
Developers provide me a simple build, then I have to instrument this build with TestComplete. Why you saying that developers have to eject something????
I instrumenting app like this https://support.smartbear.com/testcomplete/docs/app-testing/mobile/android/preparing/instrumenting-a...
according to documentation when you instrumenting the app it recompiles with PatchServices.jar.
So what else I have to do?

[JuliaBernikova]

Hi @TMbet, @cunderw,

Let me try to clarify the situation. At the moment, TestComplete indeed does not support React Native applications. The tree shown in Object Browser for the React Native Material Design demo app is a tree of native Android objects available to TestComplete after instrumenting the app. This tree, however, differs from the actual React Native structure.

Since TestComplete does not support React Native, some React Native applications cannot be instrumented correctly, so even the native Android tree is not available for them in Object Browser. @TMbet, this is the reason why for your application no tree is shown in Object Browser.

Our product team is aware of the issue and will be discussing possible improvements that should allow supporting React Native apps.

[TMbet]

Hi @JuliaBernikova ,

Finally, people can find a proper answer about the situation with ReactNative. Thank you!
This is definitely should be somewhere in TestComplete documentation about the current limitations in mobile testing. 😉 Because our team spent a lot of time investigating that problem.

#VoteReactNative

[TMbet]

Hi @JuliaBernikova ,

Does status "postponed" mean that it's not gonna happen in the near future? As I understand there is no ETA for this, right? Probably it's not an easy task.
I hope it will be selected for development one day because ReactNative is getting more important each year.

[JuliaBernikova]

Hi @TMbet,

Your understanding is correct, there's currently no definitive ETA. Our product team will revisit this task when planning future releases though - we'll be updating the request status correspondingly.