Rubberduck: Inconclusive "not the same type" unit test result should provide more information

[Irubataru]

The inconclusive test result "[expected] and [actual] values are not the same type." gives no additional information, making it very hard to identify what went wrong in a test where there are more than one assert.

Ideally it would show the values (and types) of expected and actual, but if this is difficult then it would be ok if we could simply have the assert description show so that one can easily identify which assert failed.

[mai-am]

I'd be happy to take a go at this!

[Vogel612]

@mai-am happy to hear this. You'll probably want to poke around in the AssertClass. If I understood correctly, the relevant code is Line 350.

You can find the class in the Rubberduck.Main project under ComClientLibrary/UnitTesting. It's there to register the class for COM access. There's other COM-visible unit-testing code in the same folder and the internals for Unit testing are in the Rubberduck.UnitTesting module.

[Vogel612]

Hey @mai-am it's been a week, is there anything I can do to help you?

[mai-am]

@Vogel612 Sorry! I've been having trouble running the project. Perhaps someone else wants to take a shot? Don't have a lot of time ATM.