I want to test an application which consists of multiple APKs using a single robotium project. I am not able to do it because i am not finding a way to give more than one package name in the manifest file.
Is there any solution to this ?
Can I have a single test APK to test multiple APKs ?
You cannot test an application that consist of multiple APK in a single robotium project. You can test an APK one at a time.
Related
Hello Stack Overflow community,
I'm planning to develop a UI test automation for an iOS application.
The problem is that I don't have access to the source code but only the finished ipa file of the app.
Is there a possibility to write UI tests with EarlGrey or do I need the source code of the app?
With Appium it should be possible to write UI tests without the source code.
Thanks a lot in advance!
Original EarlGrey by Google required access to iOS project, you can check here the setup.
The new EarlGrey 2 is actually has a similar concept and you need to have source code to use it.
Appium can use developer-signed .app file on simulator. If you want to run tests on real device you need have developer-signed .ipa file plus re-sign WebDriverAgent with the same iOS developer account.
So technically Appium does not require source code, but you need to have access to iOS developer certificates that been used for build
Scenario
I have two apps that are identical except for some minor textual differences. Currently I have 2x projects and would like to condense them into one.
eg.
React Native Project
/ \
Xcode build 1 Xcode build 2
Another important caveat: App Signatures
I assume the App Stores recognize app uploads by some sort of archive/compilation signature, not by app name. This is why I'm wanting to do 2 separate xcode builds rather than 1 xcode build.
Question
Can a React Native project maintain 2 separate Xcode builds?
Running multiple builds off of the same application is a pretty common paradigm in iOS development, and this holds true for React Native as well.
The instructions here should get you well on the way to configuring multiple builds, with unique bundleIds (what the app store will use to recognize it as a unique application).
To test them out on your machine after configuring everything, you can use the following command as an example.
react-native run-ios --simulator 'iPhone X' --scheme 'YOUR_SCHEME' --configuration 'YOUR_NEW_CONFIGURATION'
I would start by just duplicating your Release config and renaming it, just to make sure that it runs fine on your machine before you start playing around with the configuration.
I am new in Automating the apps for testing Android and i like to advance to this level... I have researched for Appium and Calabash... but knowing the difference pretty complicated.. There are my questions:
1: For Calabash, do we need the source code, i mean can i have APK and give test cases and so on? or do I NEED the source code even if im using the elements from app?
2: I heard i can use the Appium with cucumber, and same question do i need source code for that?
I have researched about it and all i get is for Apple apps... but nothing much for android...
You don't need source code. All you need is apk file, packageName and ActivityName to launch the app.
In Appium framework, all you need is app file (for android it will be simply .apk file).
Source code will be never needed, all elements from UI that you would like to interact with, can be simply get from Appium Inspector.
For both calabash and Appium you don't need to source code. you can automate application using apk file.
Yes you can use Appium with cucumber.
To find object locators of application use calabash console and Android UI Viewer, Appium GUI.
How to test the inbuilt android apks like camera, calculator, gallery using robotium?
I have tried but am getting error like does not have a signature matching the target. Is it possible to test the inbuilt apks using robotium?
Definitely no. For testing native Android apps try to use uiatomator test framework. Here is the link: http://developer.android.com/tools/testing-support-library/index.html#UIAutomator
I am trying to automate our build/release process. I am specifically concerned with the Android app at the moment, but I may also need to extend similar support for our iOs app.
Until now, all uploads to Crashlytics have been triggered with crashlyticsUploadDistributionRelease. However we are now building and testing the apk first, then looking to upload that same pre-built apk to Crashlytics. The new process means we need a way of uploading the apk to Crashlytics directly, without having any dependencies on rebuilding or being within the project's directory.
I can see that I can do this through Android Studio by dragging and dropping the apk. Is there a command line tool or script that I can use to automate something similar from our build machine?
This operation is not currently supported. See my comment above for the response from the Crashlytics team