[SpecFlow+ LivingDoc] LivingDoc in Azure Devops
We tried to integrate LivingDoc in Azure Devops and below are some observations:
1. We have multiple projects in our one repo. These projects has multiple test projects with multiple sets of feature files. When we publish the test for one project, it always overwrite the existing project. Do you have a solution for this?
2. We are running the automated tests using the "Visual Studio Test". We use the "Rerun failed tests" option where we rerun the failed tests. When we push the test result to livingdoc i can only see the last rerun test result. Do you have a solution for this?
-
Official comment
For the 2nd question - using the "Rerun failed tests" option - there is the following solution:
- In the LivingDoc Plugin please configure the ProcessId and ThreadId placeholders in the filepath.
You can find the documentation here.
In this case, the TestExecution.json won't be replaced if the tests re-run, because the json filename will be different for the test runs.
e.g "TestExecution_17440_26.json" - When you specify the test execution json path in the build task, define a glob pattern, that matches all the files. e.g **\TestExecution_*.json
The test result files will be merged, and you will see all the results in LivingDoc.
- In the LivingDoc Plugin please configure the ProcessId and ThreadId placeholders in the filepath.
-
Hi, thanks a lot for your feedback. If I understand your requests right, both are not supported yet, but already requested by the community.
ad 1, there is already a similar request open: https://support.specflow.org/hc/en-us/community/posts/360013799857--SpecFlow-LivingDoc-SpecFlow-Plus-LivingDocPlugin-support-for-multiple-project-execution-in-a-single-runad 2, there is already a similar request open: https://support.specflow.org/hc/en-us/community/posts/360015070297-Ability-to-see-historical-test-runs-in-Specflow-Living-Doc
Please use those two requests for upvoting the feature requests. Otherwise, let me know if I misunderstood your request.0 -
Thanks
0
Please sign in to leave a comment.
Comments
3 comments