SpecFlowOSS / SpecFlow

#1 .NET BDD Framework. SpecFlow automates your testing & works with your existing code. Find Bugs before they happen. Behavior Driven Development helps developers, testers, and business representatives to get a better understanding of their collaboration
https://www.specflow.org/
Other
2.24k stars 754 forks source link

Executing living doc cli for a .NET 6 project displays warnings #2521

Open godrose opened 2 years ago

godrose commented 2 years ago

SpecFlow Version

3.9.22

Which test runner are you using?

xUnit

Test Runner Version Number

2.4.1

.NET Implementation

.NET 6.0

Project Format of the SpecFlow project

Sdk-style project format

.feature.cs files are generated using

SpecFlow.Tools.MsBuild.Generation NuGet package

Test Execution Method

Command line – PLEASE SPECIFY THE FULL COMMAND LINE

SpecFlow Section in app.config or content of specflow.json

No response

Issue Description

See the title

Steps to Reproduce

Expected: scenarios are executed without warnings Actual: Warnings are displayed

See also the following run as a reference https://ci.appveyor.com/project/godrose/solid/builds/41525327

Link to Repro Project

https://ci.appveyor.com/project/godrose/solid

SabotageAndi commented 2 years ago

@godrose please post the warning here. The build log is too long and I didn't find it immediately.

godrose commented 2 years ago

@SabotageAndi Here you go Starting test execution, please wait... 669A total of 1 test files matched the specified pattern. 670-> Loading plugin C:\projects\solid\src\Solid.Bootstrapping.Specs\bin\Release\LivingDoc.SpecFlowPlugin.dll 671-> Loading plugin C:\projects\solid\src\Solid.Bootstrapping.Specs\bin\Release\TechTalk.SpecFlow.xUnit.SpecFlowPlugin.dll 672-> Loading plugin C:\projects\solid\src\Solid.Bootstrapping.Specs\bin\Release\Solid.Bootstrapping.Specs.dll 673-> Using specflow.json 674-> LivingDocPlugin: Output generated in: C:\projects\solid\src\Solid.Bootstrapping.Specs\bin\Release\TestExecution.json 675 676Passed! - Failed: 0, Passed: 5, Skipped: 0, Total: 5, Duration: 62 ms - Solid.Bootstrapping.Specs.dll (net6.0) 677Framework: .NET 5.0.12 678Warning: Unable to load one or more of the requested types. 679Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified. 710C:\projects\solid\src\Solid.Bootstrapping.Specs\bin\Release\LivingDoc.html was successfully generated. 711C:LivingDoc.html 7121 File(s) copied 713

SabotageAndi commented 2 years ago

Ah, this one. Yeah, that is, because the .NET Tool is .NET 5 and is loading .NET 6 assemblies. It is loading them for the unused binding part of the report. Does the feature still work for you? I don't know the behavior exactly by the hearth.

godrose commented 2 years ago

Other than the warning it does work perfectly.

On Tue, 23 Nov 2021 at 13:24 Andreas Willich @.***> wrote:

Ah, this one. Yeah, that is, because the .NET Tool is .NET 5 and is loading .NET 6 assemblies. It is loading them for the unused binding part of the report. Does the feature still work for you? I don't know the behavior exactly by the hearth.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/SpecFlowOSS/SpecFlow/issues/2521#issuecomment-976419929, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB3OIIZKHGUQGYD5H67URCTUNN2VJANCNFSM5IAFCGVA .

-- Best Regards, Gennady Verdel

diegosasw commented 2 years ago

I am having similar problems. No warnings but errors, directly. Using a .NET 6 specflow test assembly to test a .NET 6 class library.

Tests run properly but living doc is not generating. I have the tool

specflow.plus.livingdoc.cli      3.9.57       livingdoc

When running the livingdoc test-assembly

livingdoc test-assembly Rubiko.EndToEndTests.dll -t TestExecution.json
Framework: .NET 5.0.15

Warning: Unable to load one or more of the requested types.
Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
Warning: No bindings found in assembly 'C:\src\devops\my-e2e\test\My.EndToEndTests\bin\Debug\net6.0\My.EndToEndTests.dll'

Is livingdoc incompatible with the latest LTS .NET (.NET 6)?

SabotageAndi commented 2 years ago

@diegosasw these are all warnings, no errors.

ebwinters commented 2 years ago

@diegosasw the living doc is not generating? Have you checked contents of the testexecution.json file? Are your routes correct? As mentioned above those are just warnings, when I faced this issue it was due to build machine paths changing, not the livingdoc tool's fault

diegosasw commented 2 years ago

@ebwinters @SabotageAndi yes, you're right. Sorry, it was the first time I tried living doc and I thought they were errors, but the html is properly generated and working well. Thank you

kevinwee0712 commented 2 years ago

Still got heaps of warning, but living doc could be generated properly.

`Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.

Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.

Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.

Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.

Warning: No bindings found in assembly '/Users/me/development//bin/Debug/net6.0/WebTest.dll' /Users/me/development/bin/Debug/net6.0/LivingDoc.html was successfully generated. `

SabotageAndi commented 2 years ago

This will be fixed with the next version of SpecFlow+ LivingDoc

BlackGad commented 1 year ago

@SabotageAndi but where I can find release date? Or maybe you have some additional information? :)

SabotageAndi commented 1 year ago

It will be released together with SpecFlow 4. But for that we don't have also a release date. It is: when it's done

BlackGad commented 1 year ago

It will be released together with SpecFlow 4. But for that we don't have also a release date. It is: when it's done

What timeframe do you have in mind? Days, weaks, months?)

mkowal-kotrak commented 2 months ago

It will be released together with SpecFlow 4. But for that we don't have also a release date. It is: when it's done

What timeframe do you have in mind? Days, weaks, months?)

Years...