Do you have any specific requirements for the report? What information do you expect to be displayed? For now, I think we need something like a list of items that the report should include so that anyone could contribute.
Community, we are looking forward to your suggestions! :catwink:
Let’s float this topic for a couple of weeks so that our Community members could have a look and contribute.
- upon clicking on a http/ rest/ soap test step the user should be able to see the raw request/ raw response in the editor part - upon clicking on a http/ rest/ soap test step the user should be able to see the assertions and their statuses - the user should be able to see exactly why some assertion failed (eg. expected vs actual result etc) - more work has to be put into how we report other test steps types - for instance how do we report a jdbc request? how do we report a groovy script?