With the introduction of new plugin SpecFlow+LivingDoc Generator, now we can generate 2 types of LivingDoc
LivingDoc contains only the view for all the feature file (excluding test result) based on folder selected containing feature files in repository.
LivingDoc created within CI pipeline, but limited to AzureDevOps
Via SpecFlow+LivingDoc Generator,
LivingDoc contains the view for all the feature file along with test result based on project or solution selected for execution.
LivingDoc created after CD pipeline by executing test cases, using any DevOps tool like Jenkins, AzureDevOps, etc
In option 2, situation becomes different in some cases, if we just compare view in both the above cases:
Consider a solution(.sln) containing multiple SpecFlow projects(.csproj) for a single team. But every project is executed in either sequentially or parallelly on different machine. We end up with multiple LivingDoc at individual project level using SpecFlow+LivingDoc Generator for the same team. As we have no option to create a single view using multiple FeatureData.json
And, view is created only after test case execution(somewhat late in compared to option 1), but the main benefit of livingDoc lies in creating it much early in CICD stage.
Also, when we add execution result in same file it becomes much like Execution Report instead of visualization of all Feature files, which is main benefit of LivingDoc.
Can we add something like creation of LivingDoc without test execution while solution is build without dependency of AzureDevOps
Post is closed for comments.