Specflow Execution Report - Changes to MsTestToNunit.xslt file to add "Tags" as Categories in the NUnit Report #356
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
New Features: + Specflow Test execution report derived through MSTest or NUnit displays the tags attached with each scenario or feature in a seperate column viz. "Category" + Minor fix for a toggle functionality in the XSLT file to make it work consistently with IE and Chrome. New Features: + Specflow Test execution report derived through MSTest or NUnit displays the tags attached with each scenario or feature in a seperate column viz. "Category" + Minor fix for a toggle functionality in the XSLT file to make it work consistently with IE and Chrome.
This reverts commit f60e5d4.
Added "nunit:category" node for representing tags when MSTest Report(trx) is used for generating the Specflow report.
darrencauthon
added a commit
that referenced
this pull request
Sep 18, 2014
Specflow Execution Report - Changes to MsTestToNunit.xslt file to add "Tags" as Categories in the NUnit Report
gasparnagy
added a commit
that referenced
this pull request
Dec 20, 2015
… "Tags" as Categories in the NUnit Report (PR #356)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi ,
The Feature file of Specflow supports "Tags" (e.g. @sit, @sut or @JiraNumber etc) where the developers can tag their scenarios/features as required. When we use Specflow.exe with mstestexecutionreport command this information is lost while transforming the .trx file to HTML output.
Therefore I've added a XSLT code for the same which would add a node as follows under "nunit:test-case" node
The users can thus take advantage of the tags and transform the output as per their needs. Further this would help the developers and stakeholders get a quick view of their test categories.