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
When Mozilla Zest Runner is used a standalone tool to execute Zest scripts, it lacks a useful reporting. For each zest script it could leave a text file *) where each request and response are listed.
# <Number of the request starting with 1>
## Request
<URL>
<Header>
<Body>
## Response
<Status code>
<Header>
<Body>
## Assertions
[PASS | FAIL] <Test object, expected result, actual result>
Here Markdown is used. It is plain text and can be processed with usual tools (like grep) but is also human-readable. It can be converted in HTML (with limitations).
When Mozilla Zest Runner is used a standalone tool to execute Zest scripts, it lacks a useful reporting. For each zest script it could leave a text file *) where each request and response are listed.
Here Markdown is used. It is plain text and can be processed with usual tools (like grep) but is also human-readable. It can be converted in HTML (with limitations).
For machine-readable formats there is JUnit XML (https://www.ibm.com/support/knowledgecenter/en/SSQ2R2_14.1.0/com.ibm.rsar.analysis.codereview.cobol.doc/topics/cac_useresults_junit.html)
The text was updated successfully, but these errors were encountered: