Details
-
New Feature
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
open-source Jenkins 1.647 as well as the Cloubees jenkins.
Description
The Pipeline's script generator doesn't show the MSTest plugin as one of the compatible plug-in as of now. As a workaround, i am using the below batch command to get the publish working from the workflow.
[stage name: 'Publish test result', concurrency: 1
bat 'C:\\bin
msxsl.exe TestResult.trx "C:\\Jenkins\\plugins\\mstest\\WEB-INF
mstest-to-junit_withOutput.xsl" -o JUnitLikeResultsOutputFile1.xml'
step([$class: 'JUnitResultArchiver', allowEmptyResults: true, testResults: 'JUnitLikeResultsOutputFile1.xml'])]
But this involves, using the "msxsl.exe" and a .xls file for the transformation of the .trx file to .xls.
Attachments
Issue Links
- is blocked by
-
JENKINS-37159 Jenkins Pipeline support for mstest
-
- Resolved
-
- is duplicated by
-
-
- Resolved
-
Activity
Sebastian
added a comment - Everything is fine when i'm using your mstest plugin (0.19) directly (in a freestyle project).
Sorry, i was too vague. The classname tag is empty in the generated junit files. Im using the newest xUnit plugin 1.102.
Sebastian
added a comment - Everything is fine when i'm using your mstest plugin (0.19) directly (in a freestyle project).
Sorry, i was too vague. The classname tag is empty in the generated junit files. Im using the newest xUnit plugin 1.102. 
Ivo Bellin Salarin
added a comment - So, you are saying that the xUnit plugin is missing the className. You would like to have the possibility to use MSTest 0.19 in a pipelined fashion.
You have this two choices: wait two weeks for the official release of the MSTest plugin, OR test the alpha of that release.
The third solution is to contact the xUnit plugin maintainer and ask him to accept the PR I opened, which brings him the functionality of MSTest 0.19.
Ivo Bellin Salarin
added a comment - So, you are saying that the xUnit plugin is missing the className. You would like to have the possibility to use MSTest 0.19 in a pipelined fashion.
You have this two choices: wait two weeks for the official release of the MSTest plugin, OR test the alpha of that release.
The third solution is to contact the xUnit plugin maintainer and ask him to accept the PR I opened, which brings him the functionality of MSTest 0.19. Sebastian
added a comment - I'm fine with waiting for your update. Its not that urgent for me.
As the last version of the xUnit plugin is from May 2016 (i'm having no information why), i would not hope for new version soon .
Sebastian
added a comment - I'm fine with waiting for your update. Its not that urgent for me.
As the last version of the xUnit plugin is from May 2016 (i'm having no information why), i would not hope for new version soon . Ivo Bellin Salarin
added a comment - Ivo Bellin Salarin
added a comment - https://github.com/jenkinsci/mstest-plugin/releases/tag/mstest-0.20 
For those using the xUnit plugin: I have proposed a pull request to the maintainer, so he will get a few bugfixes. If it does the job you're willing to do, that's great. But, I have to admit that your example wasn't clear, and if you want to elaborate, you're welcome.