1

Topic: [xUnit] to Forward Debug. WriteLine () in ITestOutputHelper

2

Re: [xUnit] to Forward Debug. WriteLine () in ITestOutputHelper

Hello, VladCore, you wrote: VC> the Question. How not to write in each-each test class such as above the designer? A simple method: to use NUnit. Difficult: to capture text out and to drag it implicitly, something of type such. Remaining  in the same folder. Check only, the output of results falls off the version to the version at xUnit for canceled and failed tests. VC> P.P.S. And still the question - whether xUnit sorts class names and methods at serialization of performance as well as NUnit console and  ? . The standard answer on "how to make something in xUnit": it is not necessary to you. P.S. Not, it is possible to be perverted with ITestCollectionOrderer/ITestCaseOrderer, but it  is not so convenient.

3

Re: [xUnit] to Forward Debug. WriteLine () in ITestOutputHelper

Hello, Sinix, you wrote: S> the Simple method: to use NUnit. Difficult: to capture text out and to drag it implicitly, something of type such. Remaining  in the same folder. Check only, the output of results falls off the version to the version at xUnit for canceled and failed tests. Well so I and  NUnit, but it in thirds of version output deduce not smoothly as in the second, and at once all throws out only upon termination of a test method. Now only xUnit smoothly (synchronously) deduces in  output. P.S. About the interface of sorting of methods I saw. The question was about  behavior. In NUnit sorts both classes and methods alphabetically. Without any adjustments

4

Re: [xUnit] to Forward Debug. WriteLine () in ITestOutputHelper

Hello, VladCore, you wrote: VC> Well so I and  NUnit, but it in thirds of version output deduces not smoothly as in the second, and at once all throws out only upon termination of a test method. Now only xUnit smoothly (synchronously) deduces in  output. Sm here this comment and all topic entirely. Well and here it still.