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
Is the hashcode_equals_shouldWorkCorrectly test necessary due to AutoValue?
Looks like we have RunWIth(QualityMattersRobolectricUnitTestRunner.class) in lots of places where Robolectric isn't used? DeveloperSettingsTest may be the only class that actually takes advantage of Robolectric, can we remove Robolectric entirely by mocking SharedPrefs in that class?
The text was updated successfully, but these errors were encountered:
Not 100% sure - though this is not necessary however it does not hurt to have those tests. Could also be that with an update of AutoValue there's a bug (unlikely since they test their lib too) but then the regression would be detected by the CI and you won't have to bother later finding the problem.
The text was updated successfully, but these errors were encountered: