Specflow+ LivingDoc restclient error due to file size
I use the azure devops living doc plugin. We are on the latest versions.
We have one very large repo. Within it was have multiple .dll / solutions.
I was able to create a living doc pipeline to collect all the scenarios within this large repo. My issue arose when I added test results.
Since we have thousands of tests that take many hours to run, we have separate specflow pipelines to execute these tests across the span of a week. I have a single LD pipeline configured to upload the results from each of these runs (since it only allows 1 LD per repo), and then I perform multiple specflow+ livingdoc tasks to gather the results.
My problem seems to be the size of the resulting files. The file size continues to grow with each added living doc task. Regardless of the order of the LD tasks, once the resulting file hits 30MB I get this error on any LD task following the task that reached that file size.
What controls the file size max?
Is there a way to reduce the resulting file size without completely abandoning the inclusion of test results?
Could the file generation be duplicating some info causing the file to be bigger than it should? (I realize it is entirely possible that we just have too many tests, approx 3500, many of which are very large in size based on the number of test steps needed to reach the final point for which validation can occur.)
This is just a sampling of the many tasks within the Living Doc pipeline to upload results (20+) and generate the living doc (10+). Some of the solutions (.dlls) have multiple specflow execution pipelines, thus why I have more upload tasks than generate tasks.
-
I think you hit the limit of the Azure DevOps storage we are using and is available to the extensions. We infested already some time into making the files smaller, so I am not sure there is a lot of potential left. I have to ask the team.
The only workaround I can think of now is to use the SpecFlow+ LivingDoc generator CLI directly and save the files outside of Azure DevOps.
1 -
We're seeing a similar issue:
Are there any plans to resolve the size limitation, please? Are larger projects limited to the CLI implementation indefinitely?
0 -
Yes, at the moment larger projects are limited to using the CLI directly and saving the HTML somewhere else.
0 -
We are having the same problem with just 5% of our tests running.
LivingDoc for ADO was a very good feature that allowed to have all information centralized in ADO. I think without a solution for this issue LivingDoc in ADO is not very useful.0 -
We are also facing the same issue on Azure Cloud solution.
Any workaround or suggestions to get this issue fixed.
0 -
Echoing the last two comments. Running into the same issue. The file size limitation is a real problem.
0
Please sign in to leave a comment.
Comments
6 comments