Develop Reference

Excluding projects from code coverage using xUnit and coverlet

We are using Visual Studio 2022 and .Net 6.0.
We have create different test projects for each project added into the solution. And in each test project we have added xUnit and coverlet for unit test case writing and generating report.
We are writing a jenkins sonar build job to get the code coverage. This is working fine as of now but now we want exclude the projects from the code coverage and those should be displayed on sonar. So, this is how we are doing it as of now.
$SonarProjectKey = "<project key>"
Write-Host "------Sonar-Scanner Begin ------"
dotnet-sonarscanner begin /k:"<project key>" /n:"<project name>" /d:sonar.verbose="true" /d:sonar.host.url="<sonar host ur>" /d:sonar.login="<sonar login id>" /d:sonar.sourceEncoding="UTF-8" /d:sonar.cs.opencover.reportsPaths=".\coverage.opencover.xml"
Write-Host "------Sonar-Scanner Build ------"
dotnet build myproject.sln -o BuildArtifacts
dotnet test myproject.sln -o BuildArtifacts --no-build --no-restore -p:CollectCoverage=true -p:CoverletOutput=./TestResults/ -p:Exclude=\\\[.Tests]\\\ -p:CoverletOutputFormat=opencover
Write-Host "------Sonar-Scanner Ends ------"
dotnet-sonarscanner end /d:sonar.login="<sonar login id>"
However, we have tried to exclude the project by using -p:Exclude and /d:sonar.exclusions as well, but still those projects are seen on sonarqube. Below are some of the commands we have tried.
dotnet test myproject.sln -o BuildArtifacts --no-build --no-restore -p:CollectCoverage=true /p:Exclude="[MyProject.Project.Infra.*]MyProject.Project.Infra" -p:CoverletOutput=./TestResults/ -p:CoverletOutputFormat=opencover
Here above code statement, name of the project, namespace and dll is same. Still it is showing in sonarqube
So, the question how to exclude the projects which we dont want to show in sonarqube.
Also, our web api is having references of other projects. So, even if we try to exclude, those get compiled when web api project run.
Any help on this appreciated !

Azure pipeline not running NUnit tests

Just been introduced to Azure piplelines. My project is a .NET project and is linked up with Azure but does not run my Unit Tests before integrating (therefore is integrating everything even with failing tests)
My .yaml file is:
# ASP.NET Core
# Build and test ASP.NET Core projects targeting .NET Core.
# Add steps that run tests, create a NuGet package, deploy, and more:
# https://learn.microsoft.com/azure/devops/pipelines/languages/dotnet-core
trigger:
- master
pool:
vmImage: 'ubuntu-latest'
variables:
buildConfiguration: 'Release'
steps:
- script: dotnet build --configuration $(buildConfiguration)
displayName: 'dotnet build $(buildConfiguration)'
My unit tests are in the solution under a project called MyProjectTests and in a file called ProjectTests.cs. Can anyone please advise what I need to add to my yaml file (or do in general?) to get these to run please? I have looked into this myself and can't seem to find a solution and I want to avoid clogging up my commit history with failed attempts to run the unit tests.
Thanks so much.
UPDATE:
I have fixed by adding the following:
- task: DotNetCoreCLI#2
inputs:
command: test
projects: '**/*Tests/*.csproj'
arguments: '--configuration $(buildConfiguration)'

Here you go.
- task: DotNetCoreCLI#2
displayName: Test
inputs:
command: test
projects: 'PathToTestProject/TestProject.csproj'
arguments: '--configuration Debug'
You can choose whatever configuration you like, of course. And the displayName is optional. If any of your tests fail, the Pipeline will abort subsequent steps.

.NET Core Unit tests not shown in AppVeyor Tests window (and badge)

Follow up from this question, I'm currently setting up AppVeyor for my project (here) and my .NET Core tests are only shown in the console output but not in the Tests window.
This is the link for the AppVeyor project: ci.appveyor.com/project/Sergio0694/neuralnetwork-net
If some tests fail, the console correctly shows an error and the build is marked as failing, but the Tests window is empty anyways. Same goes for the badge from shields.io which shows 0 total tests, even if I can see many of them being executed from the console output.
Here's the console output:
And here's the Tests window:
Is there something else I have to setup in order for them to be reported correctly outside the console window?

Please add https://www.nuget.org/packages/Appveyor.TestLogger to your test projects.

An arguably cleaner alternative to adding an otherwise unused reference to your test project is to do this in your test script:
cd <test_project_dir>
nuget install Appveyor.TestLogger -Version 2.0.0
cd ..
dotnet test --no-build --no-restore --test-adapter-path:. --logger:Appveyor <test_project_dir>
This has the same effect as adding the reference, in that it makes the testlogger binary available to the test framework, but it doesn't actually change the test project, and therefore doesn't require someone who's not using Appveyor to install the package when they clone and build your repo.
The slight advantage of this solution over outputting and subsequently uploading .trx files (as in the PS script above) is that you should get the test results in real-time, rather than all at the end.
Example appveyor.yml:
version: 0.0.{build}
build_script:
- cmd: dotnet build MySolution.sln
test_script:
- cmd: cd Test
- cmd: nuget install Appveyor.TestLogger -Version 2.0.0
- cmd: cd ..
- cmd: dotnet test --no-build --no-restore --test-adapter-path:. --logger:Appveyor Test

You can add the AppVeyor.TestLogger package to your project, but it can be done without changing your code. You need to output your tests results into an xml file format that AppVeyor understands and then upload it to their HTTP API. The following powershell snippet will iterate through your solution and find each test project, call dotnet test on the csproj and log the output to test-result.trx and then upload the file to AppVeyor.
$config = "release"
# Find each test project and run tests and upload results to AppVeyor
Get-ChildItem .\**\*.csproj -Recurse |
Where-Object { $_.Name -match ".*Test(s)?.csproj$"} |
ForEach-Object {
# Run dotnet test on the project and output the results in mstest format (also works for other frameworks like nunit)
& dotnet test $_.FullName --configuration $config --no-build --no-restore --logger "trx;LogFileName=..\..\test-result.trx"
# if on build server upload results to AppVeyor
if ("${ENV:APPVEYOR_JOB_ID}" -ne "") {
$wc = New-Object 'System.Net.WebClient'
$wc.UploadFile("https://ci.appveyor.com/api/testresults/mstest/$($env:APPVEYOR_JOB_ID)", (Resolve-Path .\test-result.trx))
}
# don't leave the test results lying around
Remove-Item .\test-result.trx -ErrorAction SilentlyContinue
}

.NET project Nunit tests are failing during mono build

I'm pretty new to CI (from a brand new set up point at least). I created a project in Rider, using the default version of NUnit that is provided if you select to 'Create new NUnit Project', and I am now trying to set up an automated build for it using travis-CI.
The target .NET framework version of my project and test projects (confirmed in Project properties in Rider) is 4.5.
The version of Nunit I am using is the default version provided with Rider, 3.5.
Here is my .travis.yml build file:
language: csharp
solution: .sln
install:
- nuget restore FindWordsWithConcatenations.sln
- nuget install NUnit.Runners -Version 3.5.0 -OutputDirectory testrunner
script:
- xbuild /p:Configuration=Debug ./FindWordsWithConcatenations.sln
- mono ./testrunner/NUnit.ConsoleRunner.3.5.0/tools/nunit-agent.exe ./TestFindWordsWithConcatenations/bin/Debug/TestFindWordsWithConcatenations.dll
I confirmed on my own machine by running the nuget command that the test runner path should be correct, when I run the nunit-agent (via agent, agent-x86, or agent-console) I get the following error (locally, and on the server):
Unhandled Exception: System.FormatException: Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
at System.Guid..ctor(String g)
at NUnit.Agent.NUnitTestAgent.Main(String[] args)
I've also tried running with no configuration mode specified, and with configuration mode of Debug and Release specified.
Unfortunately, the normal tactic of googling/stack overflow hasn't helped, I've seen this error in a few questions, but the cause never seems related to what I'm experiencing.
The last build of the pipeline is available to view here, all the builds thus far have failed, previous builds can be seen here.
Thanks in advance, I would be very grateful if someone had any idea about the cause of this issue, or how I could tackle the test running in a different way.

Solved it.
Updated the script section of the travis config to:
script:
- xbuild /p:Configuration=Debug ./FindWordsWithConcatenations.sln
- mono ./testrunner/NUnit.ConsoleRunner.3.5.0/tools/nunit3-console.exe ./TestFindWordsWithConcatenations/bin/Debug/TestFindWordsWithConcatenations.dll
So it's now running the correct console application. Also had to modify the test paths a bit for it to run on the server.

Why can't I use 'dotnet run' with xUnit in C#?

I'm creating an application which requires unit tests. I'm using the .NET xUnit-framework.
First, I initialized a new "Hello, World! class" with
dotnet new console
Then I added the unit test
dotnet new xunit
When I run dotnet run or dotnet test, I get this error:
error CS0017: Program has more than one entry point defined. Compile with /main to specify the type thatcontains the entry point.
I read about there being a Main defined in the xUnit which interferes with the entry point in Program, but how would I be able to have these separated? That is, how would I be able to run both dotnet run and dotnet test?

You should not run both "dotnet new console" and "dotnet new xunit" in the same directory. They are different projects and they have different entry point.

Found a solution to be able to run both dotnet test and dotnet run here.
The problem is that a test project builds its own Program.cs file. You want to add following to your .csproj:
<GenerateProgramFile>false</GenerateProgramFile>