You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of the CI/CD pipeline at our company, we upload the test report folder to a large repository of test reports where the static assets are automatically served on a standard path related to which version of the tests were run. For example:
This approach needs the folder of static assets for the html report to be referenced from the index.html with a relative path (assets/index-21883a1b.js) rather than the current fixed path (/__vitest__/assets/index-21883a1b.js) so they can be served on a URL like the one shown above.
Suggested solution
When generating the HTML test report, output the paths with the expectation that the HTML report could be served from any URL and don't mandate the fixed root.com/__vitest__/report URL format.
Alternative
Provide a configuration option to choose how the report should be generated.
Clear and concise description of the problem
As part of the CI/CD pipeline at our company, we upload the test report folder to a large repository of test reports where the static assets are automatically served on a standard path related to which version of the tests were run. For example:
https://test-reports-url.com/repo_name/branch_name/build_number/<folder_of_report_assets>
This approach needs the folder of static assets for the html report to be referenced from the
index.html
with a relative path (assets/index-21883a1b.js
) rather than the current fixed path (/__vitest__/assets/index-21883a1b.js
) so they can be served on a URL like the one shown above.Suggested solution
When generating the HTML test report, output the paths with the expectation that the HTML report could be served from any URL and don't mandate the fixed
root.com/__vitest__/report
URL format.Alternative
Provide a configuration option to choose how the report should be generated.
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: