That said, I never encountered a need to investigate Log.x calls in unit tests. If you want to be rigorously strict about OOP concepts, you can extract common interface for Logger and UnitTestLogger.
Therefore, the first step will be to introduce a non-static class that will behave as a proxy for Log.x calls: /** * This class is a non-static logger */ public class Logger PowerMock, which you should avoid at all costs).
But Log.x calls are static, so you can't override them (without resolving to e.g. What you can do in unit tests is inject "test doubles" into tested components. Logcat output will not be seen in unit tests because Logcat is Android feature - JUnit tests can use only standard Java, therefore Android features won't work.
0 kommentar(er)
