Android testing against the release version of an app - android-testing

What is the correct way to run Espresso tests against the release version of my app?
If I change the build variant to release,
"android.support.test.runner.AndroidJUnitRunner" disappears from the
"Specific instrumentation runner" list of the "Run/Build
configurations". The error is "Cannot resolve symbol 'runner'".
If I try to run tests without the debug version of the app installed I am
getting the "Unable to find instrumentation target package" error.
Can anybody help me, please?

Related

Getting frequent Kill:9 Error in Xcode and Terminal

I have recently upgraded the Mac OS to Ventura 13.2.1 and Xcode to 14.2, now once I try to compile any application with Xcode, I am getting Kill:9 related issue for random task/framework in the project. I also get Kill:9 issue sometime on terminal as well.
Listing the errors here:
failed to read asset tags: The command `` terminated with uncaught signal 9. The command had no output.
Driver threw jobFailedWithNonzeroExitCode(9, "") without emitting errors.
Unable to execute command: Killed 9 Clang frontend command failed due to signal.
Please help me to resolve this issue/crash.
Open project in Xcode.
Build the app with Simulator (I tried with iPhone 14 Pro)
Error occurs in the build
Ideally project should have compiled without any error.
It sounds to me that the problem is with the installation of Xcode because when an unprivileged task is attempted, the OS will kill it off (with signal 9).
What I recommend is for you to re-install Xcode.
When you first run the new Xcode, it should prompt you for an administrator password in order to install system related components. Make sure you do this step. Hopefully that should then allow you to compile and run your iOS apps.

Error HE0046. Rider fails to install iOS app

When trying to debug an iOS application in Rider (macOS) I get this error message in the run window.
error HE0046: Failed to install the app 'com.company.name' on the device 'iOS 13.5 (17F61) - iPhone 8': Failed to install the requested application
If I switch to Visual Studio it works fine. I am unable to find any more information regarding this error or why it is occuring. Anyone know why this might be happening?
One of possible ways to understand what is going on during deploy - read msbuild logs.
Go to Rider Preferences: Preferences | Build, Execution, Deployment | Toolset and Build and enable this logs there:
Then deploy the app and go to this folder and read msbuild logs. Probably there is a specific error there.
Also you can compare these logs to visual studio log. Anyway anytime you can fire an issue in Rider issue tracker:
https://youtrack.jetbrains.com/newIssue?project=Rider
I fixed my issue by re cloning my repo.

Jenkins build failed with Xcode if project have test cases

'Module was not compiled for testing' when using #testable does not resolve this post issue.
I am integrating Xcode project with CI/CD by using jenkins and fastlane. My Xcode project build success if project do not have test cases. If I added my test cases then xcode build failed in jenkins with error:
error: module 'JenkinsFastlaneExample' was not compiled for testing
ScreenShot of error
In one post I found answer to set scheme flag, I made same like answer but didn't work for me.
My test cases are also successful in Xcode 11.x , iOS 13.x. tested in iPhone XR
I unable to find out why jenkins build is failed.
Demo Repo (if needed) : https://github.com/thedahiyaboy/ios_jenkins_example
Edit:
I also tried to disable my test cases from Xcode so that I can run my cases from mac system only and with hope jenkins will skip test bundles, but getting the same issue.
In jenkins, configuration was Release (by default) which was unnoticed by me, after replacing it to Debug my build is succeeded.
Reference Image:
Reference Doc:
https://plugins.jenkins.io/xcode-plugin/
Special thanks to Scriptable for giving time and efforts for solving the issue.

is 'APP' capability REQUIRED for WDA installation?

I'm trying to run an appium script with a real iOS device. I am currently getting this error:
Encountered internal error running command: Error: Unable to launch WebDriverAgent because of xcodebuild failure: "xcodebuild failed with code 65". Make sure you follow the tutorial at https://github.com/appium/appium-xcuitest-driver/blob/master/docs/real-device-config.md. Try to remove the WebDriverAgentRunner application from the device if it is installed and reboot the device.
Apparently this error is associated with security issues at noted here, but I've already completed that step and it's still not working. So then I thought maybe this is b/c my appium script does NOT set the 'APP' capability. 'APP' capability is of course is the full path to the application that is under test. The appium documentation here obviously doesn't indicate which settings are required if any. My question is will the Webdriver Agent not get installed on the device if the 'APP' capability is not set and thus throwing the error above?
You can right-click on the appium app (which is in ur application folder) you are using > show package contents > search for .xcodeproj > you will see a couple of projects including web driver. Now open web driver agent Xcode project and use an apple developer account to code sign it.
If you have already done this, then please update your question with appium capabilities that you have set.

Jenkins Archiving fails says :"You have to provide a value for either the marketing or technical version. Found neither."

I am trying to build Xcode project in Jenkins, I was able to successfully run my first Jenkins project. After compilation it gave me "app" bundle.
Now i'm trying to archive the bundle, but I'm getting the following error
"You have to provide a value for either the marketing or technical version. Found neither."
I tried playing with configuration but nothing seems to be working.
Xcode has a built-in tool called agvtool. Agvtool only works if you have "Apple generic" version system in settings.
Change the version system to "Apple generic" in target settings.

Resources