Specflow+ LivingDoc in Azure DevOps - unable to setup/have test execution results

April 21, 2021 21:24

Using

Feature Data: $(Build.SourcesDirectory)\bin\Debug\netcoreapp3.1\netcoreapp3.1\**.json

Test Execution JSON paths : $(Build.SourcesDirectory)\bin\Debug\netcoreapp3.1\netcoreapp3.1\**.json

=====================================================================

Error: No files are matching the pattern: D:\a\1\s\bin\Debug\netcoreapp3.1\netcoreapp3.1\**.json

##[error]Error: Command failed: dotnet D:\a\_tasks\SpecFlowPlus_32f3fe66-8bfc-476e-8e2c-9b4b59432ffa\0.6.859\CLI\LivingDoc.CLI.dll feature-data "D:\a\1\s\bin\Debug\netcoreapp3.1\netcoreapp3.1\**.json" --output-type JSON --test-execution-json "D:\a\1\s\bin\Debug\netcoreapp3.1\netcoreapp3.1\**.json" --output "D:\a\1\s\15143\FeatureData.json"

Error: No files are matching the pattern: D:\a\1\s\bin\Debug\netcoreapp3.1\netcoreapp3.1\**.json

Comments

12 comments

Andreas Willich

April 22, 2021 10:03
Do you really have twice `netcoreapp3.1` in the path?

Also update to 3.7.*, there are a lot of fixes and features in the updates.
0
Veeresh Bikkaneti

April 23, 2021 18:55 Edited
Andreas Willich

Yes, I have `netcoreapp3.1` twice in the path "bin\Debug\"

would you recommend updating specflow to 3.7 and livingdocs also to latest?

I tried that Livingdoc.html thus generated does not serve/load the html content; after several permutation, i downgraded it to this; this config works well in local, and fails in Azure while using specflow+Livingdoc extension.
0
Veeresh Bikkaneti

April 23, 2021 18:55
Andreas Willich may i request you to share a skeleton project that you have an example that works well in Azure +livingdocs plugin
0
Andreas Willich

April 26, 2021 09:44
Yes, always use the latest version of our products. Also we only support this, so if you run into an issue, the first thing you will hear from us is to update to the latest version.

I am not aware of any serve/load problems in LivingDoc. If you have such, please open a support ticket, that we can have a look at it.

The project that results of playing through the getting started step- by- step guide (https://docs.specflow.org/projects/getting-started/en/latest/) works in Azure DevOps and LivingDoc without problems.
0
Burak Turkman

May 20, 2021 03:02 Edited
Hi all,

I'm having a difficulty to locate the "TestExecution.json" file as well. I see that many of the example paths here show a "bin" folder path which gitignore doesn't let those output files (bin folders) upload to DevOps. How does your "bin\debug\ paths work?
1
Veeresh Bikkaneti

May 20, 2021 14:29 Edited
Burak Turkman

if you are using the older version of Specflow. you will see the FeatureData.json file.
0
Burak Turkman

May 20, 2021 14:37
Thank you for your reply Veeresh Bikkaneti,

I'm using the latest version and in my local I don't have any problem to locate TestExecution.json file by following bin\debug\netcoreapp3.1\... However, "bin" folders aren't uploaded to DevOps repositories. So, I used some wild cards like **\[Tt]est[Ee]xecution.json to find them but it didn't work either. This is the reason why I wonder how you made your bin\debug path worked in the pipeline if gitignore doesn't upload them to Azure repos.
0
Veeresh Bikkaneti

May 20, 2021 14:50 Edited
Share your project dependencies/packages.

The last time when I had issues upon updating versions;

Exit/close Visual Studio.

I was suggested to delete
1. ".nuget" folder and

2. clean the temp and

3. %temp% folders,

4. clean the bin,

Build and run to execute new set of deps.
0
Burak Turkman

May 20, 2021 15:02
Here is the NuGets:

<PackageReference Include="SpecFlow" Version="3.8.7" />
<PackageReference Include="SpecFlow.Assist.Dynamic" Version="1.4.2" />
<PackageReference Include="SpecFlow.Autofac" Version="3.8.7" />
<PackageReference Include="SpecFlow.MsTest" Version="3.8.7" />
<PackageReference Include="SpecFlow.Tools.MsBuild.Generation" Version="3.8.7" />
<PackageReference Include="SpecFlow.Plus.LivingDocPlugin" Version="3.8.35" />
0
Burak Turkman

May 20, 2021 22:00
Update: It looks like DevOps creates a temporary bin folder during a build. So, it explains why the bin/debug path works.

Also, you need to point your root file instead of your feature file if you want to get the results. What I mean, let's say your feature folder path is: Hello/HowAreYou/features. So, in this case your path should be Hello/HowAreYou. So, it will help you to generate results as well.

An absolute path approach worked for my case to locate the TestExecution.json file. Globals didn't help to locate it.
0
Andreas Willich

May 21, 2021 07:51
Burak Turkman I understood, that you want to commit and push your local generated TestExecution.json to Azure DevOps?

Is this correct?
0
Burak Turkman

May 21, 2021 16:32
Andreas Willich

Not actually, I was looking for the right path for TestExecution.json file to link in devOps. I came across several examples here with bin/Debug paths. Then, I thought that people are simply using the same path with their locals but our bin folders are ignored when we push. Then I realized that DevOps creates a temporary bin folder during build, so it explains why a bin/Debug path works in DevOps.
0

Please sign in to leave a comment.

Specflow+ LivingDoc in Azure DevOps - unable to setup/have test execution results

Comments

Didn't find what you were looking for?