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.

Sign up for GitHub

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

Jump to bottom

Add support for SpecRun test results #21

Closed
dirkrombauts opened this issue Nov 28, 2012 · 11 comments
Closed

Add support for SpecRun test results #21

dirkrombauts opened this issue Nov 28, 2012 · 11 comments
Assignees
@dirkrombauts
Labels
newfeature
Milestone
0.10

Comments

@dirkrombauts
Copy link
Member

I'm trying to find out whether SpecRun can output some easily parsable results.
dirkrombauts referenced this issue Aug 29, 2013
Enabling SpecRun test results format.
8eed5b1
@ghost ghost assigned dirkrombauts Aug 29, 2013
@elikhodadadi
Copy link

Hi,

I tried to use the specrun results for Pickles, but i couldn't. also i read this articlehttp://docs.picklesdoc.com/en/v1.0/IntegratingTestResultsFromSpecRun/ to generate a reasonable result for pickles. i change the template file but it didn't help me.

Thanks in advance.
some parts of myproject.proj and .srprofile files are in the following:
myproject.proj file:

.\myproje\features
\myproje\output
test
v1.0
specrun
.\TestReports\testresult.html
dhtml

This is my .srprofile file:

@dirkrombauts
Copy link
Member Author

Could you provide me some more data, like the versions of pickles and specrun you are using, the customized report file, the output file of specrun, and one ore two anonymized feature files? Thanks.

@elikhodadadi
Copy link

elikhodadadi commented Sep 3, 2016 •
edited
Loading

The output file of specrun is a html file.

@dirkrombauts
Copy link
Member Author

@elikhodadadi you can zip the files, or rename them as .txt

@elikhodadadi
Copy link

Hi,

did you see my files? what do you think? what is the problem?

@dirkrombauts
Copy link
Member Author

Unfortunately I did not see your files. All I am seeing is a post with empty lines followed by "the output of specrun is a html file". That is why I advised you to rename or zip your files.

@elikhodadadi
Copy link

list.txt
My_ReportTemplate.txt
sorry, I prefer to not attach the report of my tests. The output of specrun is a html file.
thanks.

@dirkrombauts
Copy link
Member Author

Hi,
I will try out your report template, probably tomorrow.
I respect your decision not to share the report of your tests. As a result, my ability to help you will be severely limited. If I do not have the report file, then I cannot use it to debug Pickles.

Perhaps you can share the following: near the end of the specrun html file (near the </body> element) the Pickles-related output should appear - between <!-- Pickles Begin and Pickles End -->. That is the relevant part of the specrun html file.

Another option: if you are willing to share (some of) the specrun html file but do not want to share it publicly, you can email the files to dirk dot rombauts at picklesdoc dot com. I will treat anything you send me as confidential.

@dirkrombauts
Copy link
Member Author

I'm sorry, I won't be able to look into this this week. I will do my best to investigate it next week.

@dirkrombauts
Copy link
Member Author

Forget about my last comment (I deleted it). I was mistaken.

@dirkrombauts
Copy link
Member Author

I'm afraid I won't be able to help you without a copy of your test result file. I'm sorry.

dirkrombauts pushed a commit that referenced this issue Jul 3, 2020
@darrencomeau
Feature/markdown output (#557)
1d17d04 
* 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
Assignees

@dirkrombauts dirkrombauts

Labels
newfeature
Projects
None yet
Milestone
0.10
Development

No branches or pull requests
2 participants
@dirkrombauts @elikhodadadi