Naming question for new version of Mocketry

But from English it not sounds like it should be occurred in past. So what correct and not long sentence can be used here? maybe:

mock had received someMessage

mock should haveReceived someMessage

And same question for verification group of message sends (at the end of test):

[mock someMessage. mock2 someMessage2] should occur

[mock someMessage. mock2 someMessage2] should occurInSameOrder

[ mock someMessage. mock2 somMessage2 ] should have beenSent

Maybe...
   [ mock someMessage. mock2 somMessage2 ] shouldve beenSent

but maybe you don't want different #shouldXXX messages.

[mock someMessage. mock2 someMessage2] were done
[mock someMessage. mock2 someMessage2] were doneInOrder

On Wed, Mar 23, 2016 at 8:39 PM, Denis Kudriashov <[hidden email]> wrote:
>
> 2016-03-23 12:38 GMT+01:00 Ben Coman <[hidden email]>:
>>
>> Maybe...
>>    [ mock someMessage. mock2 somMessage2 ] shouldve beenSent
>>
>> but maybe you don't want different #shouldXXX messages.
>
>
> Thank you too, Ben. And yes it will not follow other should expressions. But
> it would not be bad to use completely different word instead of #should

Okay, then perhaps...

[mock someMessage. mock2 someMessage2] were sent
[mock someMessage. mock2 someMessage2] were sentInOrder

[mock someMessage. mock2 someMessage2] were done
[mock someMessage. mock2 someMessage2] were doneInOrder

but then do you also need singular #was for single items?

[mock someMessage. mock2 someMessage2] expect done
[mock someMessage. mock2 someMessage2] expect doneInOrder

Expect squeezes in usage in both future and past tense...
"I expect he'll arrive soon"
"I expect he went home"

cheers -ben

2016-03-23 14:05 GMT+01:00 Ben Coman <[hidden email]>:

[mock someMessage. mock2 someMessage2] were done
[mock someMessage. mock2 someMessage2] were doneInOrder

I really like this idea. Thank's.

What about:

[mock someMessage. mock2 someMessage2] should beDone
[mock someMessage. mock2 someMessage2] should beDoneInOrder

?

This reads nicely.  What is the class of the value answered by #should?  What can you do with it? 

For example, assuming it is a record of the execution of the receiver, you could use

[mock someMessage. mock2 someMessage2] executed completely
[mock someMessage. mock2 someMessage2] executed completelyInOrder

and then #executed is meaningful, whereas #should is merely a linguistic hack.

And of course one could use #executes, but I think #executed is better; it has the sense of

[mock someMessage. mock2 someMessage2] when executed, #executes completely

2016-03-23 19:39 GMT+01:00 Eliot Miranda <[hidden email]>:

This reads nicely.  What is the class of the value answered by #should?  What can you do with it? 

It returns ShouldExpression instance which wraps receiver to execute following messages. And following messages are supposed to execute some assertions under receiver. 

For example it can be "1 should be: 2". Or in case with block: "[1/0] should raise: ZeroDivide"

And for message sends verification I tried to find something similar.

 

For example, assuming it is a record of the execution of the receiver, you could use

[mock someMessage. mock2 someMessage2] executed completely
[mock someMessage. mock2 someMessage2] executed completelyInOrder

and then #executed is meaningful, whereas #should is merely a linguistic hack.

And of course one could use #executes, but I think #executed is better; it has the sense of

[mock someMessage. mock2 someMessage2] when executed, #executes completely

Personally I would rename ShouldExpression to ExecutedBlock or ExecutedExpression, keep #should as nice syntactic sugar, but provide #executed as the standard way of creating ExecutedExpressions.  After all this is useful for more than SUnit.