Btw, I am from the French side of France…

that’s a very interesting example, but it’s also a complex one and since i’ve never needed to test such an algorithm, i don’t really have a solution that i can give you for that

i would probably try to stick with state-based testing for something like this (probably in combination with QuickNet instead of classical tests) and avoid any kind of interaction-based testing, despite the order requirement.

the exception handling strategies and logging suggestions have been put on the TODO list
no promises as to when i’ll actually write about those though

For example, suppose you need to write some form of breadth-first search… How would you go about testing that? I would assume it is not enough to simply check that it finds whatever you are looking for.. You would somehow need to test that the nodes are explored in the correct order?

Another suggestion would be something that describes how you handle exceptions (Here Im talking about some overall exception handling strategies, not just where you place try…catch blocks ) or logging in you application (What do you log? how do you log it? what level of detail should you aim for in the log? etc)..

Anyway, just some suggestions for posts.. Looking forward to your future posts..

i used to, but then you still actually have to show up :p

Good to have you back