Databinding.LivingDoc

[synapdb]

Hello all,

I would like to ask if anybody knows about the longevity of the databinding.LivingDoc.Report.CLI tool and the databinding.LivingDoc.ExecutionDataCollector NuGet package.

Both are working great with Reqnroll and are provided by the databinding company in Switzerland.

I also used the Allure reporting tool (allure-reqnroll) with the latest version of Reqnroll (migrated from SpecFlow) in some of our projects with success.

If a tester is needed for the cucumber messages effort then please do not hesitate to reach me. I am also available to contribute on the documentation side.

Thank you very much, my regards

Daniel

[304NotModified]

Is this open or closed source?

[synapdb]

No it is not. All I can see is the MIT licence for the CLI tool

…

On Thu, Mar 6, 2025 at 5:17 PM Julian Verdurmen ***@***.***> wrote: Is this open or closed source? — Reply to this email directly, view it on GitHub <#517 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3I46X3JZWNZGVKWZZZUA5L2TDCQTAVCNFSM6AAAAABYPDFL4GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENBRHE2DGMA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Daniel Brabant LinkedIn <https://ca.linkedin.com/in/daniel-brabant-51138a5> "*When the power of love overcomes the love of power, the world will know peace*" *-- Jimi Hendrix*

[traceryzhou]

I try to use those packages, but didn't work for me. because we had a few projects in one solution, one of the project contains bindings. the rest projects reference this binding project. In such setup, databinding.LivingDoc.ExecutionDataCollector can't detect the binding for feature data generation. Does anyone find a solution?

[synapdb]

Just to make sure I understand correctly.

Here is what we have in our case:

In a solution, we have a project called FEATURES which only containd feature files. The steps are implemented in other projets in the same solution.

Does this sound like what you have. If yes, I will create a similar case in GitHub and share it.

Thanks

[traceryzhou]

yes, that is right. Also the output json file can't support timestamp in file name. the test execution file generated fine with timestamp. But it will fail on the feature data generation.
By the way, I use the version is 6.3.0 from databinding and ReqnRoll is 2.3.0 now.

[synapdb]

Ok, thanks for the clarification. I will try to make a small example project for you.

…

On Mon., Mar. 24, 2025, 5:43 p.m. traceryzhou, ***@***.***> wrote: yes, that is right. Also the output json file can't support timestamp in file name. the test execution file generated fine with timestamp. But it will fail on the feature data generation. By the way, I use the version is 6.3.0 from databinding and ReqnRoll is 2.3.0 now. — Reply to this email directly, view it on GitHub <#517 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3I46X7JW322E4UAZFDNE5T2WB4B7AVCNFSM6AAAAABYPDFL4GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENRQG44DGOA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[synapdb]

Please take a look at the following exmple:

https://github.com/synapdb/ReqnrollDemoBinding

I hope that this what you meant.

Do not hesitate to contact me if you have questions.

[traceryzhou]

hi, thank you for your time. Do you open the log.txt to check the content? So the issue which I faced in that log.
this collector package also generates feature data as well. I verify three different test adapters (XUnit,Mstest,nUnit). only MSstest can print directly this error in Test explorer(inside visual studio). The rest will show in the log.txt.