I always wondered how TeamCity admits that it runs xUnit.net tests and how it knows to add a separate Test tab to the build overview after completing the build phase. Is the xUnit console console somehow responsible for this?
Finally found what is actually happening. TeamCity has its own API. I dug this piece of code from xUnit source code and it becomes clear:
https://github.com/xunit/xunit/blob/v1/src/xunit.console/RunnerCallbacks/TeamCityRunnerCallback.cs
public override void AssemblyStart(TestAssembly testAssembly) { Console.WriteLine( "##teamcity[testSuiteStarted name='{0}']", Escape(Path.GetFileName(testAssembly.AssemblyFilename)) ); }
... code omitted for clarity
Source: https://habr.com/ru/post/969890/More articles:How do I know which QNetworkReply belongs to QNetworkRequest in asynchronous design? - qtIt is not possible to implicitly convert the type "System.EventHandler" to "System.Windows.RoutedEventHandler" in C # - c #How to create your own composer compilation package - bitbucketStrophe js in the Titanium Appcelerator? - titaniumScraper with __doPostBack with url hidden link - javascriptJScrollPane - visual glitch while scrolling - javaProblems using scrapy using javascript __doPostBack - javascriptGet selected lines in JTable using AbstractTableModel - javaAccess to styles of sleeping navigation menu in bootstrap - twitter-bootstrapDDD Architecture - Where to Post Common Methods / Helpers - architectureAll Articles