Nov. 2, 2016
10:30 a.m.
2016-11-01 20:45 GMT+01:00 Attila Magyar <m.magyar3@gmail.com>:
Yes, it has different tradeoffs. For example you have to fill in the parameters even if you want to ignore them, or it is difficult (maybe impossibe) to express a parameter matcher that considers the relationship of multiple arguments (for example /allow: mock recv: #a:b:; with: [:a :b | a
b]/).
If you don't care about parameters you can use Any: socket stub connectTo: Any port: Any waitForConnectionFor: Any. Last case is a bit tricky of course but possible: mock stub a: [:arg1 | a := arg1. true] b: [:b | a > b] And it is easy to extend Mocketry for string based scenario: mock stub message: #a:b: with: [:a :b | a > b]. But I don't see value for this.