Forum Discussion
richie
Community Hero
Hey rajs2020,
It might be a little overkill and it isnt pretty (not like an .html report perhaps) but i use an event handler (to record my test evidence automatically) to create a .txt file for each teststep in each test case and it shows ALL the details.
I mean the input and output (request/response) all parameters, authentication details etc. It saves the output into separate testcase directories and creates a file for every test step, and even appends multiple runs and loops along with test status (pass/fail).
It logs all this detail whether pass or fail, i'm sure you could edit the groovy on the event handler to grab only fails, but i keep it to record everything as testevidence.
Would this be of interest at all?
Ta
Rich
It might be a little overkill and it isnt pretty (not like an .html report perhaps) but i use an event handler (to record my test evidence automatically) to create a .txt file for each teststep in each test case and it shows ALL the details.
I mean the input and output (request/response) all parameters, authentication details etc. It saves the output into separate testcase directories and creates a file for every test step, and even appends multiple runs and loops along with test status (pass/fail).
It logs all this detail whether pass or fail, i'm sure you could edit the groovy on the event handler to grab only fails, but i keep it to record everything as testevidence.
Would this be of interest at all?
Ta
Rich
Related Content
Recent Discussions
- 4 days agominhng