We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is your feature request related to a problem? Please describe.
Hello, do you think it would make sense to display the browser on which the tests have ran somewhere in the report ?
Describe the solution you'd like
Add a badge of the browser in the header after the title, it could use shields.io service
Describe alternatives you've considered
Append the name of the browser to reportPageTitle but I have no easy way to know which browser was requested when creating the configuration.
reportPageTitle
Additional context
The text was updated successfully, but these errors were encountered:
Turns out Mochawesome has zero options to customize the HTML output, you can't even add your own stylesheet !
Only solution I see is to append a custom script to modify the header after the initial render, kinda hacky...
Sorry, something went wrong.
Yeah we cant customize the current HTML report without doing something hacky.
I started to work on a fork of mochawesome, because over the years I saw some more enhancements and the repo didnt have any activity for a long time.
Will update as soon as I have something to show
No branches or pull requests
Is your feature request related to a problem? Please describe.
Hello, do you think it would make sense to display the browser on which the tests have ran somewhere in the report ?
Describe the solution you'd like
Add a badge of the browser in the header after the title, it could use shields.io service
Describe alternatives you've considered
Append the name of the browser to
reportPageTitle
but I have no easy way to know which browser was requested when creating the configuration.Additional context
The text was updated successfully, but these errors were encountered: