XtC10102000

Previous: XtC03102000 Next: XtC17102000

TimM proposes a discussion on ExpectationObject's and whether they need a flag for verification only on an expectation being set. SteveF and I have been having some discussions on this already, and ChrisCottee mentioned that he has encountered a similar thing.

TimM will bring some examples from the ConneXtra code base that shows why this happens and we can discuss alternatives e.g. 1 Just don't try and be too pure and put the flag in 1 Move the flag to the MockObject (Steve and I spiked this - with a hashtable of flags for ExpectationObject's - however it is a bit awkward). My other argument is that this only happens in a very few cases, so put an extra boolean in the MockObject, or set the expectation to null. It's better than messing up your ExpectationObject and makes the intention clearer. --SteveF 1 You don't need it - it indicates a problem with your code in the first place? JohnNolan suggested that this might be because one of your objects need splitting 1 Other ideas?

We reached some conclusions described in MockObjectsCodingStyle

Attendees:

• TimM
• TomAyerst
• PaulS, hopefully
• IvanM, hopefully
• SteveF, hopelessly
• CharlesWeir, lately, probably -- (shouldn't this be weir-ily?).
• ChrisCottee
• KeithBraithwaite, briefly
• SvenHowarth