And even if it did by some miracle return ExchangeRate, what happens when I need to mock an instance of a different interface?
即使它能够通过某种奇迹返回ExchangeRate，但是如果需要模拟另一个接口的实例，又会怎么样呢？
The ExchangeRate interface was small and simple enough that I could have easily written the mock class manually.
ExchangeRate接口很小很简单，很容易为它手工编写mock类。
Property to ExchangeRate allows client applications to more easily identify rate measure groups.
属性设置为ExchangeRate可使得客户端应用程序能够更轻松地标识比率度量值组。
Notice that at no point did I write a class that implements the ExchangeRate interface.
注意，我可没有编写实现ExchangeRate接口的类。
EasyMock is used to create an ExchangeRate object that always supplies the value 1. 5.
使用EasyMock创建一个总是提供值1.5的ExchangeRate对象。
Hurst Index and Its Application to Analysis of Exchangerate Fluctuations
赫斯特指数及其在汇率波动分析中的应用
以上图片仅供学习交流使用，版权归原作者所有，如有侵权，请与我方联系
