![]() Why “Shadow?” Shadow objects are not quite Proxies, not quite Fakes, not quite Mocks or Stubs. Using byte code instrumentation Robolectric is able to weave in cross platform fake implementations to substitute for native code and add additional APIs to make testing possible. When an Android class is instantiated, Robolectric looks for a corresponding shadow class, and if it finds one it creates a shadow object to associate with it. Each shadow can modify or extend the behavior of a corresponding class in the Android OS. ![]() Robolectric fills these gaps with a set of classes known as Shadows. Inadequate testing APIs - Android includes next to no APIs suitable for testing.Out of process calls - There are no Android system services running on your development machine. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |