tag:help.appveyor.com,2012-11-13:/discussions/problems/743-when-custom-script-uploads-test-output-it-only-shows-in-artifacts-and-not-on-the-tests-like-one-would-expectAppVeyor: Discussion 2018-10-19T08:16:43Ztag:help.appveyor.com,2012-11-13:Comment/344371382014-09-03T15:21:16Z2014-09-04T12:43:36ZWhen custom script uploads test output, it only shows in artifacts and not on the tests like one would expect (Pester)<div><p>Based on <a href=
"http://www.appveyor.com/docs/running-tests">http://www.appveyor.com/docs/running-tests</a>
:</p>
<blockquote>
<p>Uploading XML test results</p>
<p>Testing frameworks can produce XML report with test results.
Upload these XML files from your build script to Test results
endpoint and they will be parsed and test results added to Tests
tab of build console.</p>
</blockquote>
<p>But when I upload my test results, you can see that it adds the
xml to the artifacts, but there are no tests parsed.</p>
<p><a href=
"https://ci.appveyor.com/project/ferventcoder/chocolatey/build/1.0.11">
https://ci.appveyor.com/project/ferventcoder/chocolatey/build/1.0.11</a><br>
<a href=
"https://ci.appveyor.com/project/ferventcoder/chocolatey/build/1.0.11/tests">
https://ci.appveyor.com/project/ferventcoder/chocolatey/build/1.0.1...</a><br>
<a href=
"https://ci.appveyor.com/project/ferventcoder/chocolatey/build/1.0.11/artifacts">
https://ci.appveyor.com/project/ferventcoder/chocolatey/build/1.0.1...</a></p>
<p>Pester outputs xml compliant with NUnit, so I selected the nunit
parser for upload, but I have no visibility into why it is failing
to parse the output.</p>
<p>Perhaps it could be something key is missing for the nunit
output from pester to be correctly parsed, but this works in
TeamCity NUnit parser, so it's expected that it would also work
here.</p></div>ferventcodertag:help.appveyor.com,2012-11-13:Comment/344371382014-09-03T15:31:26Z2014-09-03T15:31:26ZWhen custom script uploads test output, it only shows in artifacts and not on the tests like one would expect (Pester)<div><p>Will take a look what's wrong.</p>
<p>-Feodor</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/344371382014-09-03T16:01:24Z2014-09-03T16:01:24ZWhen custom script uploads test output, it only shows in artifacts and not on the tests like one would expect (Pester)<div><p>Much appreciated.</p></div>ferventcodertag:help.appveyor.com,2012-11-13:Comment/344371382014-09-03T17:56:33Z2014-09-03T17:56:33ZWhen custom script uploads test output, it only shows in artifacts and not on the tests like one would expect (Pester)<div><p>OK, found the problem.</p>
<p>Parser expects <code>test-suite</code> element with
<code>type="Assembly"</code> attribute while pester's output has
<code>type="Powershell"</code>. It's been fixed. Will deploy an
update later today.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/344371382014-09-04T03:58:55Z2014-09-04T03:58:55ZWhen custom script uploads test output, it only shows in artifacts and not on the tests like one would expect (Pester)<div><p>AppVeyor update deployed. Uploading Test.xml should be working
now.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/344371382014-09-04T12:43:12Z2014-09-04T12:43:12ZWhen custom script uploads test output, it only shows in artifacts and not on the tests like one would expect (Pester)<div><p>That looks beautiful, thanks so much!</p>
<p><a href=
"https://ci.appveyor.com/project/ferventcoder/chocolatey/build/1.0.26/tests">
https://ci.appveyor.com/project/ferventcoder/chocolatey/build/1.0.2...</a></p></div>ferventcoder