CharliePoole

@rprouse We should check to see if this is an engine problem and, if so, whether we have already resolved it for the 3.5 release. I seem to remember that...

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...

@CMALD Regarding your first issue... TestContext output not working under OneTimeTearDown... This is incorrect. It is working exactly as designed. Your code is adding the screen shots for every test...

@CMALD Regarding your seond issue... Description not displaying... Is there some documentation that suggests the description will display in the output window? This would surprise me. I would expect the...

@nunit/core-team I'm not crazy about how this beta GitHub transfer works. The original issue just disappears. OK in some cases, but not in others.

Me neither! That's why this had to be transferred to the adapter repo where @OsirisTerje will see it and hopefully tell us! Personally, as a user, I think the Output...

As an example... [TearDown] public static void CleanupDriver() { TestContext.AddTestAttachment(@"C:\Screenshots\1.Jpeg" , "Description Test Attachment"); TestContext.Out.WriteLine("Test End!!!"); foreach(var key in Drivers.Keys) { Drivers[key].Quit(); } } This, because it's `TearDown` rather than...

Many users add descriptions to all or the majority of their tests. Displaying those descriptions in the Output window would obviously be confusing. However, I see you are not talking...

Are you using any nunit features to tailor the names of your tests? Are parts of those test names randomly generated?