Skip to content

Reporting #176

@mgmechanics

Description

@mgmechanics

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).

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)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions