I am passing some xss scripts through my story file which breaks the reports. do you have any work around for that.

[murthysp]

No description provided.

[simzar]

I have solved it by creating a separate properties file XSS-examples.properties, remove XSS scripts from My-Scenario.story examples section and add references to properties:

Examples:
|name   |
|name1  |

Whereas they get loaded in the definitions file
someSteps.setName(properties.getProperty("name1"))

And the properties file looks like

name1=<SCRIPT SRC=http://xss.rocks/xss.js></SCRIPT>
name2=<IMG SRC=javascript:alert('XSS')>
name3=<IMG SRC=`javascript:alert("RSnake says, 'XSS'")`>
<...>

This is not a pretty way, but it helps you to achieve the result - test the XSS injection and successfully generate a report.

[wakaleo]

The Serenity reports are not really designed to be XSS-proof, and there is only so much escaping that can be done. Feel free to take a look at the Freemarker templates if you can find a tweak that would work better for you.