stf
robolectric
Our great sponsors
stf | robolectric | |
---|---|---|
4 | 8 | |
13,134 | 5,793 | |
0.4% | 0.4% | |
0.0 | 9.8 | |
11 months ago | 2 days ago | |
JavaScript | Java | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
stf
-
Why Android developers no longer need Windows USB drivers
Hah I did the opposite.
I set up an OpenSmartphoneTestFarm (openSTF) instance at the office so people working from home could fully control smartphones inside the office to debug wifi issues. Because some countries had lockdowns at different times, so it could be that production users could work in the office but some of our support people couldn't.
It worked pretty well actually. https://openstf.io/
But they dropped support on it and moved to another product (device farmer) which never seems to have materialised at all. I don't know what happened to it but we just kept running openstf until the end of the pandemic. It worked fine anyway.
-
Access to a physical device for development and/or debugging
Did you know this exists? https://openstf.io/
-
I Mass Refactored Our Production Codebase Without Fear
* OpenSFT (Smartphone Test Farm): https://github.com/openstf/stf
I will submit the article version with more details when I finish it.
-
How I Mass Refactored Our Production Codebase Without Fear
OpenSFT (Smartphone Test Farm): https://github.com/openstf/stf
robolectric
-
Best libraries for Android Developers
Robolectric
-
What should the View layer be responsible for in Android?
Do you use Robolectric to test string resolving?
-
Testing Jetpack Compose with Robolectric
@Config(instrumentedPackages = ["androidx.loader.content"]) is a workaround for https://github.com/robolectric/robolectric/issues/6593
-
Testing Jetpack Compose without emulator or device
There is also an issue with Robolectric which can be worked around by adding @Config(instrumentedPackages = ["androidx.loader.content"]) annotation to the test class.
-
Trouble with room migrations
If it's failing only on robo, this might be the cause: https://github.com/robolectric/robolectric/issues/6411
-
How else do you test your apps, apart from Unit Testing?
Unit tests. ~X0,000. These run on the jvm (not Android), via http://robolectric.org/
-
Where do you write the test class in your classes that need context?
Take a look at http://robolectric.org. It has a specific JUnitRunner class for running unit tests in the test package with shadow classes for Android objects like application context. It is broadly used and there are a lot of examples on github and robolectric provides several themselves
- Robolectric 4.5 Beta 1 is now available
What are some alternatives?
appium - Cross-platform automation framework for all kinds of your apps built on top of W3C WebDriver protocol
JUnit - A programmer-oriented testing framework for Java.
PowerMock - PowerMock is a Java framework that allows you to unit test code normally regarded as untestable.
selendroid - "Selenium for Android" (Test automate native or hybrid Android apps and the mobile web with Selendroid.) Join us on IRC #selendroid on freenode. Also confirm you have signed the CLA http://goo.gl/pAvxEI when making a Pull Request.
robotium - Android UI Testing
Cafe - A powerful test framework for Android
robolectric - Android Unit Testing Framework
assertj-android - A set of AssertJ helpers geared toward testing Android.
LiveData Testing - TestObserver to easily test LiveData and make assertions on them.