1. -.05

2. false in both cases, baceuse object.Equals and equality operator on objects uses reference equality: first string is interned, while second is not. So they are two different objects.

3. false, in case when Id is actual identifier of Child.

That said, I still think that there's some value in commiting 'some' of those assumptions. For those cases we could move them from 'scratchpad' and to a more persisted area. Maybe an assumptions folder. Some people is against testing libraries others than your own, but I see some value on doing that. But I also see value in splitting them from your tests. Assumptions can serve as documentation and  to test for regressions (e.g. NHibernate breaking our previous assumptions on every release). We could even make assumptions about existing bugs on our dependencies and identify when the bug is fixed on a new release.

For quick and transient assumptions I like using Mono's REPL or the REPL Add-in for VS. I'll give LinqPad a go.


var host = container.Kernel.GetSubSystem(SubSystemConstants.DiagnosticsKey) as IDiagnosticsHost;
var diagnostic = host.GetDiagnostic<>();
var misconfigured = diagnostic.Inspect();

foreach (var handler in misconfigured)
{
var message = ((ComponentStatusDebuggerViewItem)ComponentDebuggerView.BuildFor(handler).Extensions[2].Value).Message;
// .…
}


Is there any way to change/force Windsor to place on misconfigured list object with not injected properties f.ex (class Foo with property ILog where ILog was not registrated)? When I don't register ILog I don't get any error using this method. Or am I missing something (optionality in property injection)?