Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><em>(Update: Mockito has added Android support as of version 1.9.5 and EasyMock has added Android support as of version 3.2 by factoring out those bits that generate code at runtime and making them pluggable, e.g. by using dexmaker instead of cglib.)</em></p> <p>Except for <a href="http://code.google.com/p/android-mock/" rel="noreferrer">android-mock</a> mentioned by DixonD (which is a fairly young, unproven library), there currently is no solution. You can immediately forget anything based on CGLib (<a href="http://code.google.com/p/mockito/" rel="noreferrer">Mockito</a>, plain <a href="http://easymock.org/" rel="noreferrer">EasyMock</a>), since CGLib relies on byte code generation and won't work on Dalvik (it also relies on the Java Beans package, which is also not part of Android).</p> <p>For what it's worth, you could use the very few mock classes coming with Android (like <a href="http://developer.android.com/reference/android/test/mock/MockContext.html" rel="noreferrer">MockContext</a>), but they don't verify behavior, they're just stubs. Their default behavior is to throw a runtime error in every method, so you have to subclass them and override the methods you want to mock.</p> <p>However, you can still use mocking libraries in non-instrumentation tests, i.e. in your standard unit tests executed on the JVM. You can use <a href="http://code.google.com/p/powermock/" rel="noreferrer">PowerMock</a> to mock framework methods, it has support for mocking static methods and constructors, making the mocking as powerful as e.g. in Ruby (just more painful to use).</p> <p>We use JUnit 4 + PowerMock + Mockito and mock out classes like Context and TextUtils in a base class from which we inherit every normal JUnit test. For instrumentation tests, we create custom mock classes and decide using a factory which implementation (mock or not) to instantiate at runtime.</p>
    singulars
    1. This table or related slice is empty.
    1. POMocking library/framework that works best in Android?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USZoFreX
    1. USMatthias
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMocking library/framework that works best in Android?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou've written that you use Mockito to mock Context - how you are doing that contrary to your first paragraph (that it can't be run because it relies on CGLib)
      singulars
      1. PO
      1. USpixel
    2. COWe distinguish between tests running on the JVM and instrumentation (UI unit and story tests) which run on the emulator (i.e. the Dalvik VM). For instance, our API connector has a dependency on a Context, but the unit test for that class is not executed on the emulator, so we can mock out the Context using Mockito and Powermock. Anything that involves running an Activity though has to be run on the emulator, where these libraries won't work.
      singulars
      1. PO
      1. USMatthias
    3. COI've updated the last paragraph to clarify our approach to this.
      singulars
      1. PO
      1. USMatthias
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload