It is not possible to instrument the App in monkey talk pro - android

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)

Related

stuck on creating 'moor_database.g.dart'

I wanted to generate file 'moor_database.g.dart' by typing the command 'flutter packages pub run build_runner watch' but after doing some procedures it just tells: [INFO] Succeeded after 9.0s with 0 outputs (4 actions)
And inside the terminal results I saw this warning:
[WARNING] moor_generator:moor_generator on lib/data/moor.dart: Missing "part 'moor.g.dart';".
I had this message because I had my own file called moor.dart which conflicted with the moor library file (that's why that command was not working properly) but Android Studio didn't give any direct errors or warning on that, after renaming my file name, everything worked

Jenkins aws device farm pugin unable to find artifact / apk

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?

Error -1073740940 when running UITest on device or emulator

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.

Unable to ‎WebKit Layout Tests‎ on android

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

Jenkins unable to locate files on my computer

when ever I try to build my android project on jenkins it fails by saying :
Started by user anonymous
Building in workspace /home/tanzeelrana/git/eventmatrix-cordova-app/mysteryshopper_version2
[mysteryshopper_version2] $ ant -Dlabel=trial1-9 clean debug
Buildfile: /home/tanzeelrana/git/eventmatrix-cordova-app/mysteryshopper_version2/build.xml
BUILD FAILED
/home/tanzeelrana/git/eventmatrix-cordova-app/mysteryshopper_version2/build.xml:90: Cannot find /home/tanzeelrana/android-sdk-linux/tools/ant/build.xml imported from /home/tanzeelrana/git/eventmatrix-cordova-app/mysteryshopper_version2/build.xml
Total time: 0 seconds
Build step 'Invoke Ant' marked build as failure
Finished: FAILURE
on line 90 in my build.xml file I have a tag with the following in it :
import file="/home/tanzeelrana/android-sdk-linux/tools/ant/build.xml"
does anyone know why it is unable to locate this file ? the file exist at the exact path ....
Jenkins usually runs with its own user (jenkins),
so it is probably an issue of permissions.
Try printing the current user from within your Jenkins job.
EDIT:
See here about running Jenkins as a daemon -
it also shows how to set it to run as a different user than 'jenkins':
Installing Jenkins as a Unix daemon

Categories

Resources