chevron-thin-right chevron-thin-left brand cancel-circle search youtube-icon google-plus-icon linkedin-icon facebook-icon twitter-icon toolbox download check linkedin phone twitter-old google-plus facebook profile-male chat calendar profile-male
0 votes
What about adding some overload methods with one more argument in which we can write text and it will be shown along with the VerifyException message
something like
.ExpectSet("prop","descriptive text")

it will be usefull for using it with loops
asked by tolisss (28.8k points)

4 Answers

0 votes
What about adding some overload methods with one more argument in which we can write text and it will be shown along with the VerifyException message
something like
.ExpectSet("prop","descriptive text")

it will be usefull for using it with loops


Hi, Sounds like an interesting idea,
So when will the message be displayed?
When the call wasn't made or when the arguments don't match.
answered by richard (3.9k points)
0 votes
i can't se the problem why it can't be implemented in both cases

ps I have asked Scott for allowing me to have the newer beta that allows mocking on costructor but haven't any news on that
answered by tolisss (28.8k points)
0 votes
i can't se the problem why it can't be implemented in both cases

ps I have asked Scott for allowing me to have the newer beta that allows mocking on costructor but haven't any news on that


Hi,
We will consider this in future releases.
Version 2.1 should be out by the end of the week, so we don't have any beta version right now.
answered by richard (3.9k points)
0 votes
Hi,
:D Part of this feature has been added to version 2.2.
It is now possible to add custom messages to argument verifications.
answered by richard (3.9k points)
...