-
Bug
-
Resolution: Unresolved
-
Major
-
Windows 7 - 32bit, 64bit
The VsTestRunner plugin allows you to run unit test via vstest.console.exe and it fails the job (or marks it as unstable) when a test fails, but it does not publish the test results like a junit job does. If you want to know how many tests have run, or why something failed, you have to check the console output.
Using the vstest.console.exe of VS2013 and /Logger:trx you get a trx file that the mstest plugin, which has a "Publish mstest test result report" post build task, cannot interprete: see JENKINS-19360.
- is related to
-
JENKINS-19360 Missing classname when used with reports generated from VSTest.Console.exe
-
- Open
-
[JENKINS-21424] VsTestRunner plugin: test results are not published
Glenn V
created issue -
Glenn V
made changes -
| Description |
Original:
The VsTestRunner plugin allows you to run unit test via vstest.console.exe and it fails the job (or marks it as unstable) when a test fails, but it does not publish the test results like a junit job does. If you want to know how many tests have run, or why something failed, you have to check the console output. Using the vstest.console.exe of VS2013 and /Logger:trx you get a trx file that the mstest plugin cannot interprete: see JENKINS-19360. |
New:
The VsTestRunner plugin allows you to run unit test via vstest.console.exe and it fails the job (or marks it as unstable) when a test fails, but it does not publish the test results like a junit job does. If you want to know how many tests have run, or why something failed, you have to check the console output. Using the vstest.console.exe of VS2013 and /Logger:trx you get a trx file that the mstest plugin, which has a "Publish mstest test result report" post build task, cannot interprete: see JENKINS-19360. |
Glenn V
made changes -
| Link | New: This issue is related to JENKINS-19360 [ JENKINS-19360 ] |
| Workflow | Original: JNJira [ 153290 ] | New: JNJira + In-Review [ 178484 ] |