-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
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
Behave html report name #23
Comments
You can set the title attribute of the What would be your preferred way of setting a custom document title? |
I am new to Behave , not sure how to write syntax for the approach you mentioned above. Please help. |
You'd have to write your own formatter, inheriting from HTMLFormatter, overriding the Alternatively, find out an elegant way how to make the Either way, you have to do some (substantial) programming, I'm afraid. – I hope that helps. |
The # -- FILE: behave.ini
# CONVENTION: Use "behave.formatter.<FORMATTER_NAME>." as scope prefix for userdata parameters
[behave.user_data]
behave.formatter.html.report_name = "My report name"
behave.formatter.html.xxx = 123 These formatter specific Userdata parameters can be supplied/overwritten by a user (on the command-line or in the config-file, like: $ behave -f html -D behave.formatter.html.report_name="My Report Name" features/ SEE ALSO: |
I would like to offer you an alternative html formatter under behave-contrib which is behave-html-pretty-formatter that supports this feature. I believe that it is not out of place to say that this project will no longer be receiving updates from our team (@modehnal @fpokryvk @schidlo ) since we have opted to do a complete re-implementation from scratch in form of a new formatter mentioned above. New formatter is much easier to maintain and improve with new features. We have opted to not do the changes in this project to provide a choice for those who prefer this version. |
can we customise the report name which appears on the report. Currently it is displayed as 'Behave Test Report'
The text was updated successfully, but these errors were encountered: