NUnit 3.0 Support

[rdbartram]

1. Description

I would like to bring in support for NUnit 3.0 among other reasons, I just wrote the whole thing to extend the Export-NUnitReport cmdlet to include properties and output fields. I noticed after writing that that we are currently NUnit 2.5 compliant and that means I can't include the output property

3. Expected Behavior

should be able to export NUnit 3.0 report

4.Current Behavior

Only exports NUnit 2.5

5. Possible Solution

I can rewrite the testresults.ps1 to either replace support for 2.5 with 3.0 or we provide a parameter somewhere for the user to choose.

Have a solution in mind?

https://github.com/rdbartram/pester/

6. Context

After the test file has been uploaded in VSTS it is easier troubleshoot when more information is saved in the test file.

[nohwnd]

That would be nice. The OutputFormat allows the user to choose the output format, to be used, please add NUnitXML30 and implement your changes.

[rdbartram]

Understood. I'll start working on it

[nohwnd]

@rdbartram Are you still interested in doing this?

[nohwnd]

Related #301

[nohwnd]

This migration should also address the problem raised in #1083 , should the fail be reported with Failed or Failure?

[rdbartram]

I had this as part of my TestCase Output PR but then removed it for separation of concern. As soon as I get the other PR in and I know that I can get a PR into pester, I'll create the next one. The code is still on my machine working internally

[nohwnd]

@rdbartram it's still unclear to me how to do the testcases properly, that's why it's still not merged. If you already have the code for this issue, could you PR that? /cc @davinci26