Skip to content

Conversation

@samtstern
Copy link
Contributor

@amandle PTAL

Embarassingly we haven't been running our tests at all, so much so that I only now realized that Robolectric does not support API 24.

I made some changes to make all the tests pass again, but it requires a downgrade of the compileSdkVersion (and therefore a downgrade of the support libraries).

Since we have no Android N features I don't think this should cause any problems, and developers can always override our support lib dependency if they are using N features heavily.

WDYT? I think having green tests on Travis is worth it.

This necessitated an SDK downgrade from M to N since
Robolectric does not yet support API 24. While it seems
strange to go backwards here, it's important that these
tests pass and there's no workaround I'm aware of.

Change-Id: I479000e18581d6b7c36eb3929ba73f12fcff0be0
Change-Id: Ic2d3db1fbdbc1a62b06f5481f4a30bf8944c80d9
Change-Id: I745c2bb2915da4342fc4452cc90cf12a59c4e045
Change-Id: I9cd6226cf3e724582ae479cc0bf016098d1b89ee
@samtstern
Copy link
Contributor Author

cc @morganchen12, getting things test-y

@samtstern samtstern added this to the 0.5.0 milestone Aug 18, 2016
@samtstern
Copy link
Contributor Author

@amandle any thoughts on this?

@amandle
Copy link
Contributor

amandle commented Aug 19, 2016

LGTM, I can't think of any reasons why downgrading would cause issues and getting the tests running is pretty crucial. Thanks for doing this!

@samtstern samtstern merged commit 710cdef into firebase:master Aug 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants