search

fluffynuts / quackers

A console logger for dotnet test with super-duck-powers!
BSD 3-Clause "New" or "Revised" License
0 stars 1 forks source link

Usable with vstest.console.exe? #3

Open thbeu opened 3 months ago

thbeu commented 3 months ago

I wonder if your logger can be used as additional logger for running C++ tests via vstest.console.exe? Thank you!

vstest.console.exe  /ListLoggers
Microsoft (R) Test Execution Command Line Tool Version 17.10.0 (x64)
Copyright (c) Microsoft Corporation.  All rights reserved.

The following Test Logger Add-Ins are available:
Microsoft.TestPlatform.Extensions.BlameDataCollector.BlameLogger
        Uri: logger://Microsoft/TestPlatform/Extensions/Blame/v1
        FriendlyName: Blame
Microsoft.VisualStudio.TestPlatform.Extensions.HtmlLogger.HtmlLogger
        Uri: logger://Microsoft/TestPlatform/HtmlLogger/v1
        FriendlyName: Html
Microsoft.VisualStudio.TestPlatform.Extensions.TrxLogger.TrxLogger
        Uri: logger://Microsoft/TestPlatform/TrxLogger/v1
        FriendlyName: Trx
fluffynuts commented 3 months ago

Hi

As far as I understand, it should be able to run for anything vstest runs, though I'm using it via dotnet, but I think that invokes the same path as vstest? I'm assuming you're writing managed C++ - try referencing the package & specifying the logger on the commandline - I'm interested to know (:

Just bear in mind that the aim of this logger is to produce better output by replacing output from the standard console logger - but I've found that there are a few messages which are emitted by the test process despite disabling the standard console logger, so ymmv. I deal with this via zarro - a tasking library with a lot of convention-over-configuration and configuration via environment variables, wherein I can manually suppress unwanted lines (that's what the configurable prefixes are for - so that zarro can set 'em, filter them out & filter out lines without the prefixes altogether)

Please report back here if you give it a go?