support optional request/response pairs for web service testing

[ericdriggs]

Use case: api testing where may interact with multiple web services

request/response is the most useful information in debugging test failures, especially when can compare to previous success/failures

Should be supported in both hierarchy.xsd and events.xsd

Implementation:
separate properties as strings.
By leaving the request/response unstructured this supports any protocol and sub-division of data.

[whytox]

Hi @marcphilipp I am going to implement this sort of functionality for a personal project, if you are interested and think that can be generally useful we can agree on a spec and I'll provide a PR.

I was thinking of tackling it by implementing an ad-hoc Contributor and a report entry handle logic on junit side (plus some frontend code eventually), just as you did for the stdout sources.

Let me know if you are interested.

[marcphilipp]

I wonder if the existing data attachment support (backed by report entries in JUnit) isn't sufficient and only needs to be documented for this use case. WDYT?

[whytox]

I guess you are right, I can try attachments first and see how good they fit for this application. Thank you 👍🏼