search

keeganwitt / gmock

Automatically exported from code.google.com/p/gmock
6 stars 2 forks source link

Strict Ordering #50

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Support for strict ordering like:

def mock = mock()
strict {
  mock.a()
  mock.b()
}

Original issue reported on code.google.com by julien.g...@gmail.com on 1 Feb 2009 at 11:47

GoogleCodeExporter commented 9 years ago

Original comment by JohnnyJianHY on 1 Feb 2009 at 11:53

GoogleCodeExporter commented 9 years ago

Original comment by JohnnyJianHY on 20 Feb 2009 at 9:15

GoogleCodeExporter commented 9 years ago 
Error messages of strict ordering will be implemented in issue 65.

Original comment by JohnnyJianHY on 27 Feb 2009 at 12:55

GoogleCodeExporter commented 9 years ago 
I discuss this functionality with a college and it look that using the strict 
keyword
is a bit meaningless. Maybe we should look at mockito and use:
inOrder {
  noOrder {
  }
}

Original comment by julien.g...@gmail.com on 16 Mar 2009 at 10:11

GoogleCodeExporter commented 9 years ago 
"inOrder" is fine, but "noOrder"...

Original comment by JohnnyJianHY on 16 Mar 2009 at 11:26

GoogleCodeExporter commented 9 years ago 
We could also pick "ordered" & "unordered" or "inOrder" and keep "loose". You 
choose.

Original comment by julien.g...@gmail.com on 16 Mar 2009 at 6:35

GoogleCodeExporter commented 9 years ago 
I would like to pick "ordered" & "unordered" as there are no capital letters in 
them.

Original comment by JohnnyJianHY on 17 Mar 2009 at 7:23

GoogleCodeExporter commented 9 years ago 
Yes you are right.

Original comment by julien.g...@gmail.com on 17 Mar 2009 at 7:28

GoogleCodeExporter commented 9 years ago

Original comment by JohnnyJianHY on 17 Mar 2009 at 7:31

GoogleCodeExporter commented 9 years ago

Original comment by JohnnyJianHY on 17 Mar 2009 at 11:10