I have created a class with the Espresso Test, named InsertFirst.class, I have correctly tried it on my android studio project, and it works.
Now I am trying to do the same on Bitrise. I have this worflow:
Activate SSH key (RSA private key)
Git Clone Repository
Bitrise.io Cache:Pull
Do anything with Script step
Install missing Android SDK components
Android Lint
Android Unit Test
Android Build for UI Testing
[BETA] Virtual Device Testing for Android
Android Build
Deploy to Bitrise.io - Apps, Logs, Artifacts
Bitrise.io Cache:Push
All the steps works, a part of the step 9. That I have configured in this way:
But when I run a build I get this ouptup on this step:
Configs:
- AppPath: /bitrise/deploy/app-debug.apk
- TestTimeout: 900.000000
- FlakyTestAttempts: 0
- DownloadTestResults: false
- DirectoriesToPull:
- AutoGoogleLogin: false
- EnvironmentVariables:
- ObbFilesList:
- TestDevices:
---
Model API Level Locale Orientation
Nexus6 24 en portrait
---
- TestType: instrumentation
- TestApkPath: /bitrise/deploy/app-debug-androidTest.apk
- InstTestPackageID:
- InstTestRunnerClass: com.app.name.nameeapp.ui.login.InsertFirst
- InstTestTargets:
- UseOrchestrator: false
Uploading app and test files
- (1/1) running
- (0/1) running
=> Test finished
Test results:
Model API Level Locale Orientation Outcome
Nexus6 24 en portrait failure
And If I go to the Test Report, on the Firebase TestLab -> Test Artifacts -> instrumentation.results
I got this error:
INSTRUMENTATION_STATUS: id=ActivityManagerService
INSTRUMENTATION_STATUS: Error=Unable to find instrumentation info for: ComponentInfo{com.app.name.nameeapp.test/com.app.name.nameeapp.ui.login.InsertFirst}
INSTRUMENTATION_STATUS_CODE: -1
android.util.AndroidException: INSTRUMENTATION_FAILED: com.app.cerere.cerereapp.test/com.app.name.nameeapp.ui.login.InsertFirst
at com.android.commands.am.Am.runInstrument(Am.java:890)
at com.android.commands.am.Am.onRun(Am.java:400)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:51)
at com.android.commands.am.Am.main(Am.java:121)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:262)
Why? I miss something in the step? Or there is something that I forgot? Thanks
Related
I am using jenkins to do the build for a Android project which works fine but uploading the apk to device farm results in a IOException as the plugin can't find the file.
Build Log
[AWSDeviceFarm] Using Project 'Android SDK2'
[AWSDeviceFarm] Using DevicePool 'Test Devices'
[AWSDeviceFarm] Using App '/AndroidSDK/PlayerSDK/build/outputs/apk/androidTest/debug/PlayerSDK-debug-androidTest.apk'
[AWSDeviceFarm] Unable to find artifact java.io.IOException: Expecting Ant GLOB pattern, but saw '/AndroidSDK/PlayerSDK/build/outputs/apk/androidTest/debug/PlayerSDK-debug-androidTest.apk'. See http://ant.apache.org/manual/Types/fileset.html for syntax
Build step 'Run Tests on AWS Device Farm' marked build as failure
Finished: FAILURE
I have tried changing application path to
**/build/outputs/apk/androidTest/debug/PlayerSDK-debug-androidTest.apk
and
**/PlayerSDK-debug-androidTest.apk
but this leads to "No artificats found at this location" error. Any ideas?
When running a Xamarin Android UITest either in the device or in the emulator I'm getting the return code -1073740940 on ADB.exe.
Test Name: AppLaunches
Test FullName: UITest1.Tests.AppLaunches
Test Source: d:\documents\visual studio 2015\Projects\UITest1\UITest1\Tests.cs : line 34
Test Outcome: Failed
Test Duration: 0:00:18,392
Result StackTrace:
at Xamarin.UITest.Shared.Processes.ProcessRunner.Run(String path, String arguments)
at Xamarin.UITest.Shared.Android.Commands.CommandAdbInstallPackage.Execute(IProcessRunner processRunner, IAndroidSdkTools androidSdkTools)
at Xamarin.UITest.Shared.Execution.Executor.Execute[TDep1,TDep2](ICommand`2 command)
at Xamarin.UITest.Shared.Android.LocalAndroidAppLifeCycle.InstallApps(ApkFile[] apkFiles)
at Xamarin.UITest.Shared.Android.LocalAndroidAppLifeCycle.EnsureInstalled(ApkFile appApkFile, ApkFile testServerApkFile)
at Xamarin.UITest.Android.AndroidApp..ctor(IAndroidAppConfiguration appConfiguration)
at Xamarin.UITest.Configuration.AndroidAppConfigurator.StartApp(AppDataMode appDataMode)
at UITest1.Tests.BeforeEachTest() in d:\documents\visual studio 2015\Projects\UITest1\UITest1\Tests.cs:line 22
Result Message:
SetUp : System.Exception : Failed to execute: D:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -s 022AQQ7N45014727 install "C:\Users\NB15664\AppData\Local\Temp\uitest\a-2B6E82A0AC77924F988970B83F62C1E372AA00FF\final-02F6B92052E860F661D6071DDD9EC4F95C4ED181.apk" - exit code: -1073740940
pkg: /data/local/tmp/final-02F6B92052E860F661D6071DDD9EC4F95C4ED181.apk
Success
The output windows gives me this:
Test Name: AppLaunches
Test Outcome: Failed
Result Message:
SetUp : System.Exception : Failed to execute: D:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -s 022AQQ7N45014727 install "C:\Users\NB15664\AppData\Local\Temp\uitest\a-2B6E82A0AC77924F988970B83F62C1E372AA00FF\final-02F6B92052E860F661D6071DDD9EC4F95C4ED181.apk" - exit code: -1073740940
pkg: /data/local/tmp/final-02F6B92052E860F661D6071DDD9EC4F95C4ED181.apk
Success
Result StandardOutput: Full log file: C:\Users\AppData\Local\Temp\uitest\log-2016-04-20_16-43-10-687.txt
Skipping IDE integration as important properties are configured. To force IDE integration, add .PreferIdeSettings() to ConfigureApp.
Android test running Xamarin.UITest version: 1.0.0
Running in unactivated mode. Test run will be restricted to simulators for a maximum duration of 15 minutes. The full version is available for Xamarin Test Cloud customers, for more information contact sales#xamarin.com.
Initializing Android app on device 022AQQ7N45014727 with apk: d:\documents\visual studio 2015\Projects\UITest1\app-debug.apk
Signing apk with Xamarin keystore.
If I send the APK for remote test execution it works and passes.
What can possibly be the issue?
Replacing my adb.exe from 20/04/2016 17:13 to one from 20/08/2015 13:21 solved the issue.
Thanks.
I am getting the below error when i start the test server. The steps I followed are:
1) calabash-android resign features\com.whatsapp-v2.12.114-450480-Android-2.1.apk
2) calabash-android build features\com.whatsapp-v2.12.114-450480-Android-2.1.apk
Done signing the test server. Moved it to test_servers/55a1d403d4a789d5d979742ac47bc35c_0.5.10.apk
3)adb devices
List of devices attached
192.168.231.101:5555 device
4) calabash-android console features\com.whatsapp-v2.12.114-450480-Android-2.1.apk
5) irb(main):001:0> start_test_server_in_background
Then i see the below error..Please help
Starting calabash-android console...
Loading C:/Ruby193/lib/ruby/gems/1.9.1/gems/calabash-android-0.5.10/irbrc
Running irb...
*** WARNING: You must use ANSICON 1.31 or higher (https://github.com/adoxa/ansicon/) to get coloured output on Windows
irb(main):001:0> start_test_server_in_background
Starting: Intent { act=android.intent.action.MAIN cmp=com.whatsapp.test/sh.calaba.instrumentationbackend.WakeUp }
Error type 3
Error: Activity class {com.whatsapp.test/sh.calaba.instrumentationbackend.WakeUp} does not exist.
RuntimeError: Could not remove the keyguard
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/calabash-android-0.5.10/lib/calabash-android/operations.rb:567:in `block in wake_up'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/retriable-1.4.1/lib/retriable/retry.rb:27:in `perform'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/retriable-1.4.1/lib/retriable.rb:9:in `retriable'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/calabash-android-0.5.10/lib/calabash-android/operations.rb:566:in `wake_up'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/calabash-android-0.5.10/lib/calabash-android/operations.rb:590:in `start_test_server_in_background'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/calabash-android-0.5.10/lib/calabash-android/operations.rb:133:in `start_test_server_in_background'
from (irb):1
from C:/Ruby193/bin/irb:12:in `<main>'
irb(main):002:0>
the keyguard is basically the feature that allows locking your android phone (with or without PIN). calabash has builtin code to handle unlocking on your phone in this case as long as the phone is not locked by pin\password.
check if your device is locked using pin\password and remove it
When I am trying to instrument the App in monkey talk it shows the following error in the console. anyone know how to solve it?
: ERROR: Process exited with an error: 1 (Exit value: 1)
instrumented APK file was not created at: /tmp/tmp_AndroidInstrumentor1398773468466_12/Caprabo_Modified/bin/Caprabo_Modified-debug.apk
Error instrumenting apk '/home/nandakishore/Desktop/Caprabo_Modified.apk': instrumented APK file was not created at: /tmp/tmp_AndroidInstrumentor1398773468466_12/Caprabo_Modified/bin/Caprabo_Modified-debug.apk
com.gorillalogic.monkeytalk.instrumentor.android.AndroidInstrumentor$InstrumentationException: instrumented APK file was not created at: /tmp/tmp_AndroidInstrumentor1398773468466_12/Caprabo_Modified/bin/Caprabo_Modified-debug.apk
at com.gorillalogic.monkeytalk.instrumentor.android.AndroidInstrumentor.copyInstrumentedApk(AndroidInstrumentor.java:235)
at com.gorillalogic.monkeytalk.instrumentor.android.AndroidInstrumentor.beginInstrumentation(AndroidInstrumentor.java:199)
at com.gorillalogic.monkeytalk.instrumentor.android.AndroidInstrumentor.instrumentApk(AndroidInstrumentor.java:130)
at com.gorillalogic.monkeytalk.ide.instrumentor.InstrumentApkAction$InstrumentApkJob.run(InstrumentApkAction.java:137)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Compile the chromium for Android
Build every test:
$ ninja -C out/Release
Running the layout Tests
$ webkit/tools/layout_tests/run_webkit_tests.sh
I get following errors:
Using port 'chromium-linux-x86_64' Test configuration: Placing test results in
/host/chromium/src/webkit/Release/layout-test-results Baseline search
path: chromium-linux -> chromium-win -> generic Using Release build
Pixel tests enabled Regular timeout: 6000, slow test timeout: 30000
Command line:
/host/chromium/src/third_party/WebKit/out/Release/DumpRenderTree -
Found 29487 tests; running 28395, skipping 1092. Unable to find test
driver
at /host/chromium/src/third_party/WebKit/out/Release/DumpRenderTree
For complete Linux build requirements, please see:
http://code.google.com/p/chromium/wiki/LinuxBuildInstructions
Build check failed
Support for layout tests on Android is being worked on at the moment. See https://code.google.com/p/chromium/issues/detail?id=232044