You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generally, I would not be in favor of adding a dependency like RoboElectric given the numerous outstanding issues with the tool, but in the case of this Library, it's benefits will outweigh the cons. My thoughts are:
We can move to full unit tests for the library
We can emulate multiple Android SDK levels and easily test against an array of them as necessary
We can generate a full code coverage report without having to aggregate across unit + instrumentation tests from different devices with different SDK levels
Travis CI with emulators absolutely sucks
I foresee this being an interim solution and would consider Firebase TestLab or another similar service as being the ultimate end goal.
The text was updated successfully, but these errors were encountered:
Generally, I would not be in favor of adding a dependency like RoboElectric given the numerous outstanding issues with the tool, but in the case of this Library, it's benefits will outweigh the cons. My thoughts are:
I foresee this being an interim solution and would consider Firebase TestLab or another similar service as being the ultimate end goal.
The text was updated successfully, but these errors were encountered: