Best practices for testing on older devices #407
Unanswered
TheBeruriahIncident
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
It seems ideal to test across different SDK versions, particularly if you support older devices and have code that branches based on what SDK is available. However, Junit 5 required Android SDK 26, and Junit 6 requires SDK 35. Only about a third of devices use SDK 35+ right now.
That seems to suggest that if you keep your Junit dependency up to date, you can't test the way the majority of devices will experience your app. It seems ideal for Junit to require as low an SDK as possible, although I appreciate that Junit isn't thinking about that, because it isn't Android-specific, which leaves this wonderful library caught in the middle.
Does anyone have any advice on how to manage this tension? My intuition is to just pin to Junit 5, as more thorough testing is probably more valuable than an up-to-date testing library.
Beta Was this translation helpful? Give feedback.
All reactions