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

Tests results not shown #19

Closed
kkrac opened this issue Nov 25, 2012 · 5 comments
Closed

Tests results not shown #19

kkrac opened this issue Nov 25, 2012 · 5 comments

Comments

@kkrac
Copy link

kkrac commented Nov 25, 2012

Hi

Not sure if I'm doing something wrong or what. It's the first time I use Pickles and am trying it with the latest version of Specflow (1.9.1)

I run pickles like this:

C:\Users\kevin\Pickles\src\Pickles\Pickles.CommandLine\bin\Debug\
pickles.commandline --feature-directory:C:\Users\kevin\MyProject\Src\Sample\Src\Sa
mple.Acceptance\Features --output-directory:C:\Users\kevin\MyProject\Src\Sample\Re
ports\Acceptance\UI\Browser\output --trfmt=nunit --lr=C:\Users\kevin\MyProject\Src
\Sample\Reports\Acceptance\UI\Browser\20121124.xml

The Html Pickles document is generated successfully. But even though I specify the link-results-file parameter (it's valid, the Xml exists) Pickles does not add the outcome of the test to the Html it generates.
Maybe I'm mistaken about what the link-results-file is for? My understanding is that it's for Pickles to specify the outcome of the tests in the document it generates? If I'm correct, then why it doesn't show it? I tried generating a Word document instead of an HTML, and still can't see the tests outcome.

@dirkrombauts
Copy link
Member

Hi,
Would it be possible to share the files so we can try to reproduce this issue? Or if they contain confidential data, could you perhaps create a sample that does not use confidential data? Thanks!

@x97mdr
Copy link
Member

x97mdr commented Nov 26, 2012

Hi,

I think I see the problem in your command line. You are using --trfmt and --lr whereas it should be -trfmt and -lr. The short versions of the arguments need only a single hyphen. The full version of the argument needs the two hyphens. Last week I committed some changes to the runners to make them report the configuration as it was read in to help identify issues like this. Can you try changing your command line to this and see if it works:

C:\Users\kevin\Pickles\src\Pickles\Pickles.CommandLine\bin\Debug\
pickles.commandline --feature-directory:C:\Users\kevin\MyProject\Src\Sample\Src\Sa
mple.Acceptance\Features --output-directory:C:\Users\kevin\MyProject\Src\Sample\Re
ports\Acceptance\UI\Browser\output -trfmt=nunit -lr=C:\Users\kevin\MyProject\Src
\Sample\Reports\Acceptance\UI\Browser\20121124.xml

Thanks

@kkrac
Copy link
Author

kkrac commented Nov 26, 2012

I tried that but it didn't work. I still don't see the results in the Html generated by Pickles.

Find below the feature and XML files

thanks.


  • Script to run pickles:

C:\Users\user\Pickles\src\Pickles\Pickles.CommandLine\bin\Debug\pickles.commandline --feature-directory:C:\Users\user\MyProject\Src\Sample\Src\Sample.Acceptance\Features --output-directory:C:\Users\user\MyProject\Src\Sample\Reports\Acceptance\UI\Browser\output -trfmt=nunit -lr=C:\Users\user\MyProject\Src
\Sample\Reports\Acceptance\UI\Browser\20121125.xml


https://github.com/kkrac/ProSpec/blob/master/Src/Sample/Src/Sample.Acceptance/Features/PageNotFound.feature

https://github.com/kkrac/ProSpec/blob/master/Src/Sample/Src/Sample.Acceptance/Features/UserAccount/Confirm.feature

https://github.com/kkrac/ProSpec/blob/master/Src/Sample/Src/Sample.Acceptance/Features/UserAccount/Create.feature

https://github.com/kkrac/ProSpec/blob/master/Src/Sample/Src/Sample.Acceptance/Features/UserAccount/Login.feature

@x97mdr
Copy link
Member

x97mdr commented Nov 27, 2012

I think I see your problem. This is the HTML report file, not the XML
report file from NUnit. How are you running NUnit?

On Mon, Nov 26, 2012 at 12:03 PM, kkrac [email protected] wrote:

I tried that but it didn't work. I still don't see the results in the Html
generated by Pickles.

Find below the feature and XML files

thanks.

  • Script to run pickles:

C:\Users\user\Pickles\src\Pickles\Pickles.CommandLine\bin\Debug\pickles.commandline
--feature-directory:C:\Users\user\MyProject\Src\Sample\Src\Sample.Acceptance\Features
--output-directory:C:\Users\user\MyProject\Src\Sample\Reports\Acceptance\UI\Browser\output
-trfmt=nunit -lr=C:\Users\user\MyProject\Src

\Sample\Reports\Acceptance\UI\Browser\20121125.xml

XML Report file:
https://github.com/kkrac/ProSpec/blob/master/Src/Sample/Reports/Acceptance/UI/browser/20121125.xml

Feature files:

https://github.com/kkrac/ProSpec/blob/master/Src/Sample/Src/Sample.Acceptance/Features/PageNotFound.feature

https://github.com/kkrac/ProSpec/blob/master/Src/Sample/Src/Sample.Acceptance/Features/UserAccount/Confirm.feature

https://github.com/kkrac/ProSpec/blob/master/Src/Sample/Src/Sample.Acceptance/Features/UserAccount/Create.feature

https://github.com/kkrac/ProSpec/blob/master/Src/Sample/Src/Sample.Acceptance/Features/UserAccount/Login.feature


Reply to this email directly or view it on GitHubhttps://github.com//issues/19#issuecomment-10723698.

@x97mdr
Copy link
Member

x97mdr commented Nov 27, 2012

I'm going to close this issue now but feel free to move the discussion to the newsgroup if you need help using NUnit to generate an XML report. Here is the relevant section for the nunit.console.exe command-line runner, which is what I use: http://www.nunit.org/index.php?p=consoleCommandLine&r=2.6.2. I reproduced it here:

Specifying the XML file name

As stated above, the console program always creates an XML representation of the test results. To change the name of the output file to "console-test.xml" use the following command line option:

        nunit-console /xml:console-test.xml nunit.tests.dll
Note: For additional information see the XML schema for the test results. This file is in the same directory as the executable and is called Results.xsd.

@x97mdr x97mdr closed this as completed Nov 27, 2012
dirkrombauts pushed a commit that referenced this issue Jul 3, 2020
* Corrected mistake and enhanced consistency in the CONTRIBUTING page.

* Added new project for Markdown unit tests with initial, inconclusive, test.

* Added another new project for Markdown acceptance tests with initial, inconclusive, test.

* Initial hook up of Markdown builder and first feature, adding a Title.

* Added Markdown document resolver

* Refactored, concerns seperated into Stylist and TitleBlock classes.
Static text placed in localization resource file for future translations.
Some aspects still in builder for later refactoring when the path is clearer.

* Updated build scripts to include Markdown library and tests

* fix test.fsx error for Markdown.UnitTests reference

* Downgrade Specflow to 2.3.2 to attempt build issue fix.

Included partial work on Generated Info feature.

* Corrected UnitTests namespace, added PicklesDoc. prefix.

* Generation Time tested with new TestableDateTime singleton.

Ready for refactoring.

* Refactor Generation Info, now part of TitleBlock and Localization.

* Implemented File Location feature. Scenario: Output is written to specified location

* Minor cleanup in Markdown acceptance tests feature and steps

* Feature Heading added to Markdown output

* Feature Description added to Markdown output

* Corrected line spacing for feature description

* Feature Tags included in Markdown Output

* Scenario Heading added to Markdown document

* Added Scenario Tags to Markdown output

* Confirm order of content in Markdown output for this acceptance testing

* Steps in Scenarios added to Markdown output

* Refactor code, documents have lines and different blocks which share a
parent class all return collections of lines.

* Feature Background included in Markdown Output

* New Scenario Outline Feature.

Table formatting moved to own class TableBlock
ScenarioOutline formatting added in class ScenarioOutlineBlock

* Fixed bug #19 - Couldn't write markdown output file
Fixed bug #20 - Tags have double @ symbols

* Fixed bug #21 - Scenario Outlines missing placeholders
- In steps
- In Tables

* Include Markdown icon files in output folder

* Scenario Result included in heading.

Stylist updated to process ScenarioHeading TestResult.
Updated ScenarioBlock to process TestResult values.

Acceptance tests updated to test Scenario Status

* Table construction now incudes results when available e.g. in scenario outline examples.

* Markdown Stylist updated to include results and code refactored.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants