Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Json reports are not consistently same #1547

Closed
manavghaigithub opened this issue Dec 23, 2019 · 4 comments
Closed

Json reports are not consistently same #1547

manavghaigithub opened this issue Dec 23, 2019 · 4 comments

Comments

@manavghaigithub
Copy link

I opened a ticket for Json plugin and below is the link for the same. Its been 6 days and nobody responded to me so thought of opening a ticket here to see if somebody can take a look at the issue.
getgauge-contrib/json-report#14

Problem Statement --> Json plugin, for the same test, sometimes shows steps details and sometime shows details only at spec level.

I ran my test twice and both the times the report is different. In one report i see that all the step details are present but the second report does not has any step detail. The behavior is inconsistent.

It is happening for both 0.3.0 and 0.3.2

Attached are the files for your reference.
Json.Results.zip

Expected behavior

The Json structure should be same

Actual behavior

The Json structure is not same

Gauge version

Gauge version: 1.0.4
Commit Hash: 3a9a647

Plugins

dotnet (0.1.2.nightly-2019-02-14)
html-report (4.0.7)
json-report (0.3.0)
screenshot (0.0.1)
xml-report (0.2.1)

@negiDharmendra
Copy link
Contributor

negiDharmendra commented Jan 14, 2020

@manavghaigithub I have tried with the versions you have mentioned as well as with the latest Gauge and other plugins installed from the source. Every things is working fine.

Is it possible for you to share a project to replicate this issue and provide a fix.
Note: Please upgrade the Gauge and Gauge-dotnet to the latest version.

@sriv
Copy link
Member

sriv commented Feb 11, 2020

@manavghaigithub - were you able to sort this out?

@negiDharmendra
Copy link
Contributor

@manavghaigithub Please feel free to reopen this issue if you are still facing it.

@manavghaigithub
Copy link
Author

manavghaigithub commented Feb 18, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants