question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Meta Data section in the scenario JSON

See original GitHub issue

Objective

  • This will help to capture any comments or useful information about authors or ticket(jira story) or a test category etc.

The section could look like below-

{
    "scenarioName": "Scenario Verify Person REST apis as well as DB layer",
    "ignoreStepFailures": false,
    "steps": [
        {
            "name": "get_enitity",
            "url": "/api/v1/people/visa/{id}",
            "method": "GET",
            "request": {
            },
            "assertions": {
                "status": 200
            }
        }
    ],
    "meta": {
        "authors": ["Emma", "Sidd", "Krish"],
        "tickets": ["ISSUE-519", "GT-312"],
        "categories": ["dev", "sit1", "sit2"],
        "others":["Runs every day", "Need to speak to Security team"]
        // and so on...
    }
}

  • Show these in the reports etc.

Issue Analytics

  • State:open
  • Created 5 years ago
  • Comments:7 (2 by maintainers)

github_iconTop GitHub Comments

2reactions
aghorpadecommented, Feb 27, 2019

@authorjapps - metdata tag is associated with steps or should it be associated with scenario? I think if we associate metadata with scenario then it will have more significance and useful too in reporting. E.g. Scenario - always comes with specific ticket and steps can have more than one steps so I think metadata should along with scenario. Suggestions?

1reaction
authorjappscommented, May 20, 2019

Hello @jneate , thanks for your interest in contributing. Seems like we will have to expand this issue a bit - will add more details soon. You can then pick it.

In the mean time(if you get chance) You can look at this bug => https://github.com/authorjapps/zerocode/issues/241 (This was definitely working earlier, but introduced in the recent releases… ie couple versions ago).

This is a minor bug - Somewhere the report builder is missing an entry.

Hope this will give a good start for the first issue ! 👍

Read more comments on GitHub >

github_iconTop Results From Across the Web

Metadata JSON Files: /Documentation - LabKey Support
A metadata file written in JSON is used to configure the fields and categories for document abstraction. The file configures the field categories...
Read more >
How to represent meta data in JSON - Stack Overflow
Note: this is a NodeJs app. I have the following JSON object that stores questions and answers:
Read more >
Metadata in block.json | Block Editor Handbook
This section describes all the properties that can be added to the block.json file to define the behavior and metadata of block types....
Read more >
Setting up JSON metadata for an output file - 8.0
This section describes how to define JSON metadata for an output file. Now you can drag and drop the file connection or the...
Read more >
Metadata - AWS CloudFormation
Use the Metadata section to add JSON or YAML objects to your template.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found