Add Summary & Breakdown of Test Result Performance to AppVeyor Output

[PlagueHO]

As a DSC resource kit contributor
I want to be able to see the amount of time spent running tests in each file/fixture
So that my test I can identify tests that might be targets for improving performance

See: dsccommunity/xPSDesiredStateConfiguration#477 (comment)

Tagging @mhendric, @johlju

[johlju]

I liked the idea of outputing a table from the NUnitXML. Start with that and see how far it gets us? I think it should be enough. 🤔

[johlju]

Maybe instead of outputting a table, maybe we can add the information to the test pane? If we made this into a helper function, when looping through the NUnitXML we could just add rows to the test pane. That way each file would be at the top of the test pane results. 🤔
I'm good with an ASCII table in the output view too 🙂

DscResource.Tests/AppVeyor.psm1

Lines 865 to 892 in bfa3d0d

	if ($PSVersionTable.PSEdition -eq 'Core')
	{
	$requestObject = @{
	testName = $addAppVeyorTestParameters.Name
	testFramework = $addAppVeyorTestParameters.Framework
	fileName = $addAppVeyorTestParameters.Filename
	outcome = $addAppVeyorTestParameters.Outcome
	durationMilliseconds = $addAppVeyorTestParameters.Duration
	}
	if ($result.FailureMessage)
	{
	$requestObject['ErrorMessage'] = $addAppVeyorTestParameters.ErrorMessage
	$requestObject['ErrorStackTrace'] = $addAppVeyorTestParameters.ErrorStackTrace
	}
	<#
	ConvertTo-Json will handle all escaping for us, like escaping
	double quotes and backslashes.
	#>
	$requestBody = $requestObject | ConvertTo-Json
	Invoke-RestMethod -Method Post -Uri "$env:APPVEYOR_API_URL/api/tests" -Body $requestBody -ContentType 'application/json' | Out-Null
	}
	else
	{
	Add-AppveyorTest @addAppVeyorTestParameters
	}

[PlagueHO]

Do you mean the AppVeyor Tests:

So you're thinking adding test summaries directly to the test results tab in AppVeyor for the run? That could definitely be worth investigating!

[johlju]

Yes exactly. If test name need to have a value then just use the filename there too. I'm thinking one entry per file, and after that all the entries is added from the pester object like it does today. Hopefully they are viewed in the same order they are added, otherwise it won't work :)