I'm trying to configure Bitbucket pipeline with dotnet core and NUnit. Everything seems to be ok, build passes, but test step fails. In pipeline logs everything is correct, every test passes and build is successful. Should I configure it differently?
I would really appreciate any ideas what is wrong :).
My project url: https://bitbucket.org/Tisu/meetupapi/addon/pipelines/home#!/
Pipeline config:
# This is a sample build configuration for .NET Core. # Check our guides at https://confluence.atlassian.com/x/5Q4SMw for more examples. # Only use spaces to indent your .yml configuration. # ----- # You can specify a custom docker image from Docker Hub as your build environment. image: microsoft/dotnet:latest pipelines: default: - step: caches: - dotnetcore script: # Modify the commands below to build your repository. - export PROJECT_NAME=.\\MeetupSchedulerCore\\MeetupScheduler\\MeetupScheduler.sln - export TEST_NAME=.\\MeetupSchedulerCore\\MeetupScheduler\\MeetupScheduler.sln - dotnet restore .\\MeetupSchedulerCore\\MeetupScheduler\\MeetupScheduler.sln - dotnet build $PROJECT_NAME - dotnet test $TEST_NAME
In the mean time I suffered similar Problems on other environments and found out that there is a problem with running NUnit Tests with the dotnet CLI.
My Solution was to switch to xUnit wich works perfectly fine and it‘s really quick to switch.
By the way: I like the approach of how a xUnit TestClass gets written much more then the NUnit approach
I sufferd an similar issue but a little diffrent.
I was able to solve it by explicit specifing the UnitTests project file for the call of dotnet test.
It works for me at the moment but I hope there is some other solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
if i am not mistaking donet test looks for .csproj location may be need to map to .csproj location?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.