How to share the generated HTML with your team?¶
The generated HTML is a single page application with no external depedencies, so it is easy to share within your team.
The possible sharing options are depending on your current infrastructure setup and needs, but here are some ideas:
- you can use any file sharing solution (Windows file share, Sharpoint, Dropbox etc.)
- you can host the generated HTML with any of the static HTML hosting services (Azure Blob Storage, AWS)
- you can directly store it in your Continuous Integration Server
Sharing with a Continuous Integration Server¶
You can use the Thrid-Party Reports feature of TeamCity to publish the HTML to your Build Results.
Currently there is no support for publishing HTML reports from a Build pipeline. You can vote for this feature request: Support for generic HTML Publishing inside Build and Release Pipelines
The recommended approach for Azure Devops is to use our SpecFlow+LivingDoc for Azure Devops extension.
As alternative solutions you can publish the generated HTML as,
- a build artifact using the Publish Build Artifacts task
- in this case the generated HTML can be downloaded from the Build Result page
- you can publish the HTML to Azure Storage following this article: Deploying a static website to Azure Storage using Azure DevOps