Usage in unit testing

When unit testing the Android app (junit.framework.TestCase or Junit 4 tests from a pure submodule) joda-time-android cannot be used as it requires a context as part of the JodaTimeAndroid.initialization.

The alternative is to obviously just use joda-time for submodules and converting TestCases to AndroidTestCases (in the process getting hold of a context for initialization).

In you experience have you had to deal with a similar case and if so did you choose an alternative nicer approach for unit testing? Conceptually it would be nice to have the exact same JodaTime library used for both testing and production, but is this just a limitation that can’t be overcome?

Cheers

[ghost]

This is a bit late but if anyone stumbles here, unfortunately not all of modules were pure java, but thankfully most of the package names and functionality in joda time android is similar to joda time, so for running jvm unit tests you can do something like

testCompile "joda-time:joda-time:${jodaTimeVersion}"

Although this won’t work for classes or modules where you are using jodaTimeAndroid exclusive classes, but in my case i was able to successfully use it in a lot of places

@dlew i am assuming there shouldn’t be any side effects with this approach like possible flaky tests

[ghost]

True, so I guess most people can do jvm tests without any problem for the most part On 20-Dec-2015 1:03 am, “Daniel Lew” [e-mail] wrote:

That’s what we do internally. In fact, nowadays joda-time-android has a transitive dependency on joda-time, so you’re using exactly the same classes. The only difference is the ZoneInfoProvider.

— Reply to this email directly or view it on GitHub https://github.com/dlew/joda-time-android/issues/17#issuecomment-166017785 .