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

report should preserve the order as of data driven table present in spec file #228

Open
h2grover opened this issue Jun 5, 2019 · 1 comment

Comments

@h2grover
Copy link

h2grover commented Jun 5, 2019

Expected behavior

During the data-driven, parallel test run order of the rows should be preserved in the reports.

Actual behavior

Please check the s.no in the screenshot

Screenshot 2019-06-05 at 3 02 28 PM

Steps to reproduce

Run this code:

Spec file:

# Spec header

tags: test

   |S.No.|url                          |
   |-----|-----------------------------|
   |1    |https://docs.gauge.org       |
   |2    |https://www.google.com/      |
   |3    |https://www.facebook.com/    |
   |4    |https://docs.gauge.org/latest|
   |5    |https://gauge.org/plugins/   |

## scenario header


* Naviagte to <url> url

step_implementation.js:

const puppeteer = require("puppeteer");
const assert = require("assert");

step("Naviagte to <url> url", async function(url) {
  const browser = await puppeteer.launch({ headless: false });

  const page = await browser.newPage();
  await page.goto(url);

  if (url.includes("latest")) assert.fail("Failed step");

  await browser.close();
});

Gauge version

Gauge version: 1.0.5
Commit Hash: 562f036

Plugins
-------
html-report (4.0.8)
js (2.3.5)
screenshot (0.0.1)
@h2grover
Copy link
Author

@Apoorva-GA I have another feature request, I guess this falls under this PR only.

Currently, the failed scenarios are showing on the top of each HTML spec file. It would be great we can preserve the scenario order also in case of any failure.

And let me know if you guys are working on this anytime soon. 🙏

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

1 participant