robolectric

I have a project that using Robolectric for unit test purpose. This project uses Robolectric 3.0 and need to add -ea and -noverify options in Virtual Machine options. In Android Studio, I created new JUnit configuration in Run > Edit Configurations... and then set VM Options to -ea -noverify . With this way I success to run my unit test. This is image about my configure, view Here However, for continuous deployment, I need run unit test with command line. So I use ./gradlew test to run unit test. I also add org.gradle.jvmargs=-ea -noverify to gradle.properties file. Unfortunately, it doesn't

I have an android app that uses ORMLite/SQLite and I use Robolectric in conjunction with JUnit 4 to allow me to run unit tests in Android Studio and on a Jenkins build server. Typically I would setup test data in my tests, in the setup, and then run my test scenarios against it but when I tried to do this I started getting issues and exceptions which seemed to be related to files being locked or something and that seems to be a problem others have had... so what I have done up until now is use the create database method in my database helper to create some dummy data which the tests expect to

I'm trying to use PowerMockito to mock some static methods in Android Robolectric tests. I'm using JUnit 4.8.2, Robolectric 2.2, Mockito 1.9.5, and PowerMock 1.9.5 as directed here . As I have to use the RoboElectricTestRunner , I'm attempting to use the PowerMockRule to bootstrap PowerMock. However I'm getting an unfortunate java.lang.IncompatibleClassChangeError when the test with PowerMock runs. java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun

The issue I have with robolectric is that it doesn't make real HttpRequests. Could I replace the HttpClient implementation of robolectric using a real one actually making the calls to my local test server? Jan Berkel submitted a pull request to Robolectric that was merged into master on March 8th. You can now call Robolectric.getFakeHttpLayer().interceptHttpRequests(false); in the beginning of your test to bypass the mocked http layer in Robolectric. You can download the jar directly from Sonatype to include in your Eclipse Android project. If you are using Maven and 1.1 has not yet been

If I write a custom Shadow for my Activity, and registering it with RobolectricTestRunner, will the framework intercept the Activity with my custom Shadow whenever it's started? Thanks. The short answer is no. Robolectric is selective about what classes it intercepts and instruments. At the time of this writing, the only classes that will be instrumented must have a fully qualified classname match one of these selectors: android.* com.google.android.maps.* org.apache.http.impl.client.DefaultRequestDirector The whole reason for Robolectric's existence is that the classes provided in the Android

I'm trying to use Robolectric in a project build with gradle inside the new Ide for android: Android studio, but I'm facing a strange problem, I've correctly imported all the libraries and created the "test" folder inside "src", the fact is that whenever I run the tests the ide keep saying "Class not found: "com.example.myandroidproject.test" what I'm doing wrong? i need to change something in the gradle.build? here's my directory structure: This is unlikely to work out of the box as src/test isn't used automatically. You'd need to create a test task automatically that compiles this source

Actually, I need to get a response of an API call, for that I required Context . Update. Just use for version 1.x and 2.x: Robolectric.application; And for version 3.x: RuntimeEnvironment.application; You can use RuntimeEnvironment.application Use this: Robolectric.application John Add testImplementation "androidx.test:core-ktx:${deps.testrunner}" And use: private val app = ApplicationProvider.getApplicationContext() To get application context you must do the following: annotate @RunWith(RobolectricTestRunner.class) RuntimeEnvironment.application.getApplicationContext() For the latest

I need to run debug while my tests execution in Android Studio + Robolectric. Each time I try to run them by selecting debug for the test task from Gradle tasks I get the error message: Error running package_name:app_name [test]: Unable to open debugger port : java.net.SocketException "Socket closed" Any ideas? Eugene I found the reason of the error. To make it run you need to uncheck the "Use in-process build" option in Compiler -> Gradle settings of Android Studio. I was getting this error on linux, and the problem was that the another previous process has taken the port and hung. So, the