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
{{ message }}
This repository was archived by the owner on Sep 25, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 25, 2026. It is now read-only.
Convert StorageImplTest from EasyMock to Mockito #270
Google requires new tests to use Mockito even if existing tests use EasyMock.
It's really hard to use two frameworks within a single test because setUp/tearDown methods invoked before and after each test perform some framework specific actions.
It's not required to convert all tests to Mockito, but the overhead of supporting both frameworks can be higher than the effort to convert existing tests.
In case of StorageImplTest, there will be many new tests developed for new Storage features, so it worths to convert these tests.
Activity
elharo commentedon Apr 17, 2020
You can always create a new test class that uses Mockito. There's no requirement that we only have one test class per model class.
dmitry-fa commentedon Apr 17, 2020
Two test classes per model class will lead to code duplication. Perhaps the right way to go is:
meredithslota commentedon Oct 10, 2023
It looks like the bulk of this work is already done in the linked PRs — @frankyn is this ok to close out?
frankyn commentedon Oct 18, 2023
Hi @meredithslota this is still an issue to move away from EasyMock.
frankyn commentedon Oct 24, 2023
Passing it over to @JesseLovelace who had been working on this issue from last fixit