Could not find a test logger with AssemblyQualifiedName, URI or FriendlyName 'GitHubActions'.

[hisuwh]

I'm getting this error Could not find a test logger with AssemblyQualifiedName, URI or FriendlyName 'GitHubActions'

I'm referencing Microsoft.NET.Test.Sdk version 16.6.0 which I believe is the latest.

Any tips on how to debug this or what I might be missing?

[hisuwh]

The dll doesn't seem to be copied to the bin folder which might be why it cannot detect it.

[Tyrrrz]

Just to make sure, are you referencing the nuget package in your test project (i.e. not main project)?

Something like this:

https://github.com/Tyrrrz/CliWrap/blob/54abad02376b98bf87b6bef5a62c103362e18107/CliWrap.Tests/CliWrap.Tests.csproj#L18-L24

[hisuwh]

Yep. Well actually I'm using a common.targets file that my test project is importing. Though I did try referencing it directly also and that did not work either.

I'm using .net core 2.1 and I see you are using 3 - wonder if that is a factor

[hisuwh]

Ok I've created a simple .NET core 3.1 project locally and I am still getting the same error so that does not seem to be relevant.

[Tyrrrz]

Does it work if you clone the project I linked and run dotnet restore and then dotnet test -l GitHubActions?

[hisuwh]

ok scrap that I'd missed the import 🤦
It does work with .net core 3.1. And I can see it copies the dll to the output.
So must be something to do with .net core < 3 😞

[hisuwh]

This is my test project with .net core 2.1 You can see the reference to your package but it does not copy it to the output folder

So then when I run the tests it does not see the logger

[Tyrrrz]

Ahh. I think .NET Core 2.1 apps and lower didn't copy their dependencies to the output folder. It can be enabled with a project property:

<CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>

[hisuwh]

Just found the exact thing myself 👍
Tested and that works. Thanks for your help and quick responses

[Tyrrrz]

You're welcome!