dotnet test not working on Linux container, but is on Windows: "An exception occurred while invoking executor 'executor://specrun/executorV3.2.31': No such file or directory"
#1991
Comments
echarrod
changed the title
dotnet test not working on Linux machine, but is on Windows: "An exception occurred while invoking executor 'executor://specrun/executorV3.2.31': No such file or directory"dotnet test not working on Linux container, but is on Windows: "An exception occurred while invoking executor 'executor://specrun/executorV3.2.31': No such file or directory"
|
In typical fashion, I've been stuck on this for days and then right after I post the issue, I manage to fix it. I removed the package 👍 |
|
You had using the SpecFlow+ Runner. One dependency to use it on Linux is to have mono installed. This is needed for the report generation. As you found a solution an this is the correct behavior (the error could be better), I am closing this issue. |
|
@SabotageAndi How do I disable report generation ? I think I have similar problem and disabling reports might help. |
|
I would first try to install the Mono dependency to get it work, because you are losing a key feature of the SpecFlow+ Runner. Disabling the reporting is documented here: https://docs.specflow.org/projects/specflow-runner/en/latest/Profile/Report.html |
|
@SabotageAndi I just spent many hours trying to figure out the cause of this same issue. Only real difference is I am using the latest version of the NuGet pkgs, WSL 2, and netcore 3.1 It would be rad if there was some way to have a better error. |
|
@GoFightNguyen And you fixed it with installing Mono? |
|
@SabotageAndi I don't want to have a dependency on mono, so I did not attempt to install it. Maybe it is because my local repo is in WSL 2 and/or because I am using VS Code (so unable to use the Visual Studio SpecFlow extension), but I had issues using mstest with SpecFlow too. At this point, I need to move on with the project so I decided to leave SpecFlow (for now) :( |
|
I also still have this issue. Mono (v 6.12.0.90) is already installed on system , as I am using VS for mac. Here is the full error |
|
@SabotageAndi I installed mono using apt-get, like so:
Which works successfully. However, I thought I would point out that the disabling of reports doesn't seem to change anything. |
|
@ZukkyBaig Linux is case-sensitive for filenames. The Filename has to be |
|
Is a way to split report generation? To SpecFlow.Plus.Runner.Reporting.exe as a parameter is passed file Is it possible? |
|
@adrusz No, this is not possible at the moment. What do you want to achieve? And did you had a look at SpecFlow+ LivingDoc? |
|
My goal is to generate a report from test execution in cucumberJson format (then it will be imported to Jira XRay) FROM mcr.microsoft.com/dotnet/sdk:5.0 as dotnet
COPY [ "./", "/src"]
WORKDIR /src
RUN dotnet restore ./TestSpecFlow.SpecRun.csproj
RUN dotnet build ./TestSpecFlow.SpecRun.csproj
RUN rm /tmp/* -R
RUN dotnet test ./TestSpecFlow.SpecRun.csproj; exit 0
FROM mono:latest as mono
COPY --from=dotnet [ "/src/bin/Debug/net5.0/SpecFlowPlusRunner/net461", "/Reporting"]
COPY --from=dotnet [ "/src/CucumberJson.cshtml", "/Templates/CucumberJson.cshtml"]
COPY --from=dotnet [ "/tmp/tmp*.tmp", "/Reporting"]
WORKDIR /Reporting
RUN mono ./SpecFlow.Plus.Runner.Reporting.exe ./tmp*.tmpBut |
|
@adrusz What is hindering you to install mono in your docker image for test execution? Then you get the report directly out to the execution and there is no need to split something up. |
|
@SabotageAndi I tied but then I had some |
|
@adrusz As we are discussing this in an already closed issue, let's move us this to a new issue or the community forum. We are spamming 4 people with notifications at the moment. |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
SpecFlow Version:
Used Test Runner
Version number: dotnet version: 3.1.202
Project Format of the SpecFlow project
packages.config<PackageReference>tags.feature.cs files are generated using
SpecFlow.Tools.MsBuild.GenerationNuGet packageSpecFlowSingleFileGeneratorcustom toolVisual Studio Version
Enable SpecFlowSingleFileGenerator Custom Tooloption in Visual Studio extension settingsAre the latest Visual Studio updates installed?
<Major>.<Minor>.<Patch>.NET Framework:
Test Execution Method:
dotnet test<SpecFlow> Section in app.config or content of specflow.json
specflow.json:
{ "bindingCulture": { "language": "en-uk" }, "language": { "feature": "en-uk" } }Issue Description
Tests run fine both when I run through Visual Studio and from command line with
dotnet teston a Windows machine.When I push to our CI system, which uses a linux based docker image:
mcr.microsoft.com/dotnet/core/sdk, which essentially just does this in the container:the tests look like they pass, but then I get the following error:
I've tried:
My csproj:
Steps to Reproduce
To follow
The text was updated successfully, but these errors were encountered: