Michaël Hompus

> Thanks for the PR! I'm assuming that addresses this method of checking for test projects? Yup, thanks for merging. > No, not currently. I'm not even totally sure what...

Maybe look at XElement type of naming? Something like `WithDescendantInnerException`

I'm looking at making the `TypeAssertions` a bit more robust. This will take quite a bite out of this list

Basically it comes down to fix the arguments for the following classes * `PropertyInfoAssertions` * `AssemblyAssertions` * `MethodInfoAssertions` * `TypeSelectorAssertions` * `XDocumentAssertions`

Have a PR prepared for `PropertyInfoAssertions` as soon #1550 is in.

I was looking into this, but I can't reproduce it for `HaveLength` ```csharp public void When_asserting_string_length_on_null_string_it_should_fail() { // Arrange string actual = null; // Act Action act = () =>...

> If you attach a debugger, you should be able to see the exception. Ah, indeed, makes it a bit harder to confirm the correct working with a red/green unit...

I could not reproduce the NRE on `BeCloseTo` to line 52 of `PollUntil`. I did find the following cases that were not detected yet: ```csharp # ExecutionTime Action someAction =...

Hi @jnyrup, I ran your test yesterday and it seems there are no error detected anymore? I did look at the code to inject `null` arrays (`new [] { null...

I think collection methods also obscure a lot as they tend to wrap `AssertionScope`s in their flow