tutorials/Android-Tutorial-Test-ShowCase
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Adjust robolectrictest instructionset

Browse source
This commit is contained in:
Gergely Hegedus 2022-04-12 16:11:34 +03:00
parent 423249f326
commit 78a877b0c9
1 changed files with 4 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

5
codekata/robolectric.instructionset.md
View file

@ -37,7 +37,10 @@ And if we run our test class we already get an exception:
So we need to mock the creation of `SharedPreferences`, then the `SharedPreferences` as well. So we need to mock the creation of `SharedPreferences`, then the `SharedPreferences` as well.
Since our classes main purpose is to handle `SharedPreferences`, that doesn't really make sense. Since our classes main purpose is to handle `SharedPreferences`, that doesn't really make sense.
Well, I would rather not do that. So then we need to test on a Real Device or Emulator. Well we could, but then we need to integrate a Testing Farm with our CI. It would be good to do that, but sometimes that's just not possible, here is where [Robolectric](http://robolectric.org/) comes in. Well, I would rather not do that. So then we need to run our tests on a Real Device or Emulator during development.
Well we could do that, but it just takes that much more time.
We would also need to to integrate a Testing Farm, or run Emulators in docker with our CI.
It would be good to do that, but sometimes that's just not possible, here is where [Robolectric](http://robolectric.org/) comes in.
>Robolectric is the industry-standard unit testing framework for Android. With Robolectric, your tests run in a simulated Android environment inside a JVM, without the overhead and flakiness of an emulator. Robolectric tests routinely run 10x faster than those on cold-started emulators. >Robolectric is the industry-standard unit testing framework for Android. With Robolectric, your tests run in a simulated Android environment inside a JVM, without the overhead and flakiness of an emulator. Robolectric tests routinely run 10x faster than those on cold-started emulators.