… value defined. When calling a expected function with invalid arguments, the expectation is not matched, but the exception does not show the args used.
…ck.Setup.AllowRedefinedBehaviorDefinitions" to true)
…cause the ExpectationMet-Flag was only set when hitting a method (which isn't the case on a "zero hit method")
…nd below. The new overload means no updates need to occur in the unit under test, just in the init section of the testing unit.
…e that would never be hit.
…eImprovement Conflicts: Delphi.Mocks.MethodData.pas Delphi.Mocks.Proxy.pas
… method mocks
…lements with TMock<object> mocks.
…Mock<T>.Verify<I> have all been fully implemented. This change allows the implementation of multiple interfaces on the one mock. The interfaces which are returned by the mock via the "instance" function will support all "implemented" interfaces set on the TMock.
QueryInterface will now work for all implemented interfaces off the object/interface returned by Instance. Only thing left to implement is the Verify<T> and VerifyAll methods. These will verify the setup of the specific implementation or all setups calls.
…'t merge into upstream yet. The main issue with the previous implementation was that it fought with Delphi's Generics implementation too much. There is a major need for interface generic methods in the way I previously worked this. Now this has been simplified so that the proxy does not know how to create its child proxies, its just given them. Its the TMock<T> record which knows how to achieve adding new proxies. There are some access violations in some tests due to this change. Pushing to code to another branch so that I can work on it later.