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

Specflow v2.0 nunitexecutionreport problem #539

Closed
bmelnychenko opened this issue Jan 27, 2016 · 16 comments
Closed

Specflow v2.0 nunitexecutionreport problem #539

bmelnychenko opened this issue Jan 27, 2016 · 16 comments
Labels

Comments

@bmelnychenko
Copy link

Nunit v3.0 generates TestResult.txt output file with "=>" symbols at the begining of each test, but your NUnitExecutionReportGenerator check for "***" symbols at the beginning, so it doesn't create console-logs in the report.

Could you tell me please when you can fix it?How long does it take?
Thanks.

@mk-meros
Copy link

mk-meros commented Feb 7, 2016

Besides lack of console logs, the html report also doesn't contain following data:

  • number of passed/failed tests
  • test status
  • test execution time, etc.

btw. XML reports from NUnit 3 contain output logs inside the XML(inside nodes). So there should be no need to use .txt any more.

When do you plan to update the report generator?
Regards

@bmelnychenko
Copy link
Author

Yes, I have found that output logs are inside xml and I've updated report generator.
But I need some html report. Earlier I used specflow nunitexecutionreport with .xml and .txt files and it generated me pretty html.
But now specflow nunitexecutionreport doesn't generate me html.
What generator can I use?
Maybe some different tools?

@vikash-gupta
Copy link

Apart from "=>" issue mentioed by @bmelnychenko, when NUnit3.0 is used to run parallel tests the text output is not sequential. Thus even if "=>" is replaced by "***" manually, when parallel tests are enabled in NUnit, SpecFlow is not able to generate HTML reports.

In our team we're running browser based tests for BDD and we want to leverage NUnit 3.0 parallel feature to run them in parallel. When can we expect these 2 issues fixed in SpecFlow?

@kappa10j
Copy link

kappa10j commented Apr 7, 2016

When will the fix be published to nuget?

@sgyves71
Copy link

sgyves71 commented Apr 7, 2016

I am also looking forward to being able to get nUnit Execution reports. This is a deal breaker change. . Bring back reporting!! Pleaaaassee!!

@vikash-gupta
Copy link

I've sent a PR for the fixes. If you want it before next release, you may checkout the source code and apply commits in the PR

The reporting works for both- sequential and parallel test case execution.
The primary change is to follow NUnit 3 recommended approach of using TestContext class

@kappa10j
Copy link

When is the next release? I work within a firm that pretty much only allows pulling from nuget.

vikash-gupta pushed a commit to vikash-gupta/SpecFlow that referenced this issue Jul 8, 2016
vikash-gupta pushed a commit to vikash-gupta/SpecFlow that referenced this issue Jul 13, 2016
@tanneerumahesh
Copy link

any update on this?

@alexeygrant
Copy link

I am too experiencing this issue. Is there a fix other than downgrading NUnit to 2.x?

@sergiorykov
Copy link

NUnit3 console runner seems canceled support of nunit2 xml reporting format (nunit/nunit-console#95). May be it's just a bug but it's time to support nunit3 xml reporting format :)

@SabotageAndi
Copy link
Contributor

@sergiorykov: You need following NuGet package: https://www.nuget.org/packages/NUnit.Console/
This include the Addin for the NUnit2 format.

@sergiorykov
Copy link

Thanks! Missed that.

@chakraborty-rupam
Copy link

Any update on this, when this will be fixed? I have Nunit3 xml reports with Attachments in the xml (Screenshots), but Specflow exe is unable to convert it.
Its really getting very difficult to have html reports with screenshots using Specflow minus SpecRun

@Stephen-Mc
Copy link
Contributor

@599139: SpecFlow is open source. If you are suffering because a feature is lacking, that is all the motivation you need to download the source code and start fixing :)

@SabotageAndi
Copy link
Contributor

Closed because of irrelevance for SpecFlow 3, since reports have been removed for now and will probably re-implemented differently.

For more details see #1036

@lock
Copy link

lock bot commented Jul 8, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests