CharliePoole

It would help me if you pointed out the specific problem you are trying to fix. "Unifying" the various pieces of code could be good, could be bad, depending. I...

Your interpretation of equality conversion is correct. We wanted `Assert.AreEqual` to work like the `==` operator for numeric values. I agree that parameter conversion and expected value conversion should work...

With the exception of start- and end-run, the events all originate in the framework, so this should be a framework issue if it's kept as an issue. The behavior is...

@nborisenko Correct. Because no cases run in that situation. I think this is a bit different from the situation that @ashishdawale20 is reporting.

I understand why it seems strange and I think (as I said above) something should be done to make it consistent. However, it is equally strange that a test that...

I should add, btw, that this is exactly why the events are called `test-case` and `test-suite` rather than `end-test` and `end-suite`! But obviously that is not enough for documentation.

@nunit/framework-team Can someone review this and either accept or reject it as an issue?

Note that some tests can actually start (be run) and then use Assert.Ignore to be ignored. It seems as Assert.Ignore and IgnoreAttribute ought to be reported in the same way.

Ah! That changes things a bit. I won't move this issue yet. You are running into a problem with two contributing causes... 1. You are adding the attachment in the...

Just to take care of the documentation part of this (since we are in the docs repo here) I updated the pages for OneTimeSetUp attribute, OneTimeTearDown attribute and TestContext so...