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
We are deploying all our test reports to github pages in different directories.
/report-integration - shows vitest
/report-e2e - shows playwright html report
The issue we are facing is that Vitest HTML report requires pathname to empty. Eg sannajammeh.github.io/. So when deployed to sannajammeh.github.io/report-integration, the UI is a complete black screen.
I tested this during development as well. Using npx vite preview --outDir ./reports serves without a pathname successfully and the tests show. When opening an HTML server using Live Server in vscode from the testing directory, the pathname is set at <live server host>/reports. Vitest loads all JS files successfully, even the gzipped test data, yet shows a black screen with no tests.
Reproduction
I think the description suffices. There is no way to reproduce with an example without hosting to a specific pathname.
Describe the bug
We are deploying all our test reports to github pages in different directories.
/report-integration - shows vitest
/report-e2e - shows playwright html report
The issue we are facing is that Vitest HTML report requires pathname to empty. Eg
sannajammeh.github.io/
. So when deployed tosannajammeh.github.io/report-integration
, the UI is a complete black screen.I tested this during development as well. Using
npx vite preview --outDir ./reports
serves without a pathname successfully and the tests show. When opening an HTML server usingLive Server
in vscode from the testing directory, the pathname is set at<live server host>/reports
. Vitest loads all JS files successfully, even the gzipped test data, yet shows a black screen with no tests.Reproduction
I think the description suffices. There is no way to reproduce with an example without hosting to a specific pathname.
System Info
Used Package Manager
pnpm
Validations
The text was updated successfully, but these errors were encountered: