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
{{ message }}
This repository has been archived by the owner on Jan 15, 2023. It is now read-only.
Currently, if Steps description contains the angle brackets (< & >), then those are replaced with < and > in ExtentCucumberAdapter (we are using version 1.0.10)
But if Scenario and Scenario-Outline description contain angle brackets (< & >), extent report is partially loading and dashboard and clickable items are not working properly. We found that it is causing issues due to unclosed HTML angle brackets (< & >) tags that are used in Scenario and Scenario-Outline descriptions.
Would it be possible to convert/replace the angle brackets (< & >) with < and > for Scenario and Scenario-Outline description content as well?
Maybe, following highlighted code segment to be updated with replacing the angle brackets.
We would really appreciate it if you could accommodate this in the next upcoming release. Thanks in advance.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, if Steps description contains the angle brackets (< & >), then those are replaced with < and > in ExtentCucumberAdapter (we are using version 1.0.10)
But if Scenario and Scenario-Outline description contain angle brackets (< & >), extent report is partially loading and dashboard and clickable items are not working properly. We found that it is causing issues due to unclosed HTML angle brackets (< & >) tags that are used in Scenario and Scenario-Outline descriptions.
Would it be possible to convert/replace the angle brackets (< & >) with < and > for Scenario and Scenario-Outline description content as well?
Maybe, following highlighted code segment to be updated with replacing the angle brackets.
We would really appreciate it if you could accommodate this in the next upcoming release. Thanks in advance.
The text was updated successfully, but these errors were encountered: