[SpecFlow+ LivingDoc] AzureDevOps - Bug? Features Linking to Other Doc Feature with Same Name
TLDR if LivingDoc is generated for a solution with multiple projects, if they have a feature in common (e.g. Login.feature) the other two projects with the same name will all point to the same feature.
We have a C# test solution for three products we are testing and each of them has their own distinct project with a folder of feature files.
All of the projects have a Login.feature.
On application build in AzureDevOps, the associated YAML file for the entire solution has tasks to look in each of the project's file paths and generate the LivingDoc.
To better explain, after building the entire solution we have three LivingDoc generation tasks like below that only differ because each reference a different project (i.e MyProjectA, MyProjectB and MyProjectC)
- task: SpecFlowPlus@0
displayName: MyProjectA Living Doc Generation
When the LivingDoc generates it has 3 top level folders MyProjectA, MyProjectB and MyProjectC to twist open with the expected features and scenarios for that project inside. However if the Feature file in MyProjectB has a Login feature and a scenario is clicked it jumps to MyProjectA's Login feature in the document. The same goes for MyProjectC. It seems that repetition of Feature and/or Scenario name within a LivingDoc generated in this way has a bug with mapping.Or is there a setting to avoid this issue?
Please sign in to leave a comment.