Hi! To make updating to the latest version easier, you have to update all SpecFlow packages together. Simply check the checkbox on the left at the package entry and press the "update" button in the middle of the screen. Sometimes the NuGet UI is a little bit confusing. Because of the version dependencies between the packages, updating them one by one doesn't work and you need to do the additional steps. Also please submit this video to our SpecFlow Community Hero Program: specflow.org/community/community-hero-program/
Great video! I am using "Scenario Outline" that pulls from an external data source (.csv file) using the SpecFlow.ExternalData NuGet but for some reason the step-level data (.csv column data for each row parsed) doesn't seem to be pulling into the LivingDoc report I'm generating... livingdoc test-assembly -t TestExecution.json is what I'm executing. Example: 13:13 I can see the same view, but I don't see "50" or "70" or "120" for the finite details when expecting them. What I am seeing instead would be something like "Given the first number is " instead of "Given the first number is 50", almost like a variable isn't being parsed as expected. Is this an issue with combining LivingDoc test report data with the SpecFlow.ExternalData plugin or am I just doing it wrong? Any feedback is appreciated!
Hello Karthik, I hope you are well. So if you link the results to the living doc (analytics tab), you can only do this for one test execution run, yes? I would like to see how you integrate this with azure devops please.
I am good mate, how are you over there in Queenstown ? I have not tried it so far as well with the new feature, but it should be straightforward as well I guess !
I'm trying to run the reports generation on my local machine with jenkins and i'm getting the error: 'livingdoc' is not recognized as an internal or external command, operable program or batch file. when running with cmd or powershell, the generations is successfull, please can you help me?
Hey Karthik, even if I installed specflow.plus.livingdocplugin, when I run the test, it does not create json file. I can not see any json file in bin/debug/netcoreapp3.1. What do you think it might cause?
Hello Kartik, I watched this video, and tried to implement spec flow liv document in project. But I am running into a problem, actually I have 3 TestExecution.json files, but merging these 3 files produces incorrect results. E.g. testExecution1.json has 5 scenarios 2 failed, I run my test again this time also failed tests fails again in TestExecution2.json file, on 3rd attempt these 2 tests case passed and testExecution3.json file is generated, In last I merge all these 3 files, but get incorrect results. Reports says 5 scenarios pass and 2 failed, total 7, but in actual total were 5 scenarios. Can you please help me into this.
@@ExecuteAutomation like does it show which .cs file is causing the failure? Do you have any example of it? In my report I can see the failure but no sign of stacktrace.
Really thankful you are keep on doing this updates ....Much much helpful
Hi!
To make updating to the latest version easier, you have to update all SpecFlow packages together. Simply check the checkbox on the left at the package entry and press the "update" button in the middle of the screen. Sometimes the NuGet UI is a little bit confusing.
Because of the version dependencies between the packages, updating them one by one doesn't work and you need to do the additional steps.
Also please submit this video to our SpecFlow Community Hero Program: specflow.org/community/community-hero-program/
Sure Andreas !
Done Andreas !
Thanks for helping Andi!
Great video!
I am using "Scenario Outline" that pulls from an external data source (.csv file) using the SpecFlow.ExternalData NuGet but for some reason the step-level data (.csv column data for each row parsed) doesn't seem to be pulling into the LivingDoc report I'm generating...
livingdoc test-assembly -t TestExecution.json is what I'm executing.
Example: 13:13 I can see the same view, but I don't see "50" or "70" or "120" for the finite details when expecting them.
What I am seeing instead would be something like "Given the first number is " instead of "Given the first number is 50", almost like a variable isn't being parsed as expected.
Is this an issue with combining LivingDoc test report data with the SpecFlow.ExternalData plugin or am I just doing it wrong?
Any feedback is appreciated!
Me pasa igual, en Living Doc no se muestran los casos de pruebas cuando se leen de un Excel.
Why should we use "LivingDoc" instead of "ExtentReports" ? what are the main benefits?
Hi @ExecuteAutomation, Is there anyway to view overall execution time on analytics tab?
How to maintain LivingDoc report History in Azure DevOps?
Hello Karthik, I hope you are well.
So if you link the results to the living doc (analytics tab), you can only do this for one test execution run, yes?
I would like to see how you integrate this with azure devops please.
I am good mate, how are you over there in Queenstown ? I have not tried it so far as well with the new feature, but it should be straightforward as well I guess !
Execute Automation : My SpecFlow tests are failing . Now, how can I make my Testing stage in Jenkins fail when SpecFlow tests are failing ?
it fail in the step when you execute dotnet test
I'm trying to run the reports generation on my local machine with jenkins and i'm getting the error:
'livingdoc' is not recognized as an internal or external command, operable program or batch file.
when running with cmd or powershell, the generations is successfull, please can you help me?
Hey Karthik, even if I installed specflow.plus.livingdocplugin, when I run the test, it does not create json file. I can not see any json file in bin/debug/netcoreapp3.1. What do you think it might cause?
Hello Kartik, I watched this video, and tried to implement spec flow liv document in project. But I am running into a problem, actually I have 3 TestExecution.json files, but merging these 3 files produces incorrect results. E.g. testExecution1.json has 5 scenarios 2 failed, I run my test again this time also failed tests fails again in TestExecution2.json file, on 3rd attempt these 2 tests case passed and testExecution3.json file is generated, In last I merge all these 3 files, but get incorrect results. Reports says 5 scenarios pass and 2 failed, total 7, but in actual total were 5 scenarios. Can you please help me into this.
Please do a video on extent reports
Does it capture screenshots of test failures?
Does LivingDoc accept stacktrace? Say at which line the code has failed?
Yap that’s correct
@@ExecuteAutomation like does it show which .cs file is causing the failure? Do you have any example of it? In my report I can see the failure but no sign of stacktrace.
@@prasannay3746 The stacktrace usually has the details of the file which had the problem, its just a dotnet thing, nothing to do with Specflow really.
where thois series? I am confuse...