Skip to content
This repository was archived by the owner on Jul 21, 2025. It is now read-only.
This repository was archived by the owner on Jul 21, 2025. It is now read-only.

Include timestamps for test cases during conversion #103

@nayanab123

Description

@nayanab123

🤔 What's the problem you're trying to solve?

The JSON file generated by the standalone json-formatter does not follow the same JSON schema as the in-built json formatter.
The property I'm specifically looking for is the start_timestamp for scenarios. This information is available in ndjson file generated by the in-built message formatter. However, it is omitted while transforming to JSON.

✨ What's your proposed solution?

Ideally, update the standalone formatter to follow the same JSON Schema as in-built JsonFormatter.
Temporary solution -> ensure start time stamps are also included in the JSON file generated after conversion from ndjson.

⛏ Have you considered any alternatives or workarounds?

I could not find any alternatives that work for maven projects.

📚 Any additional context?

Quite a lot of reporting libraries/plugins that generate stylized HTML reports for cucumber use JSON as the input. I'm yet to find one that supports ndjson inputs.
The plugin that I'm using right now takes multiple json files containing the results of reruns as input and generate a single HTML report combining the data in them. This helps in creating a consolidated report for a complete run including reruns on failed testcases. For this purpose, the plugin checks the start_timestamp attribute for testcases in cucumber JSON report to decide on how to merge the data for reporting. Since the timestamp is missing in json files created by the standalone formatter, this functionality fails.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions