Incorrect test start/end date and duration

[C0nquistadore]

Description

The test run that is published through the extension doesn't seem to correctly publish the start, end dates and duration of each test. This makes it hard to analyze, if the performance of a particular test changed over time. Looking at the pipeline logs, it seems that start and end date matches that of the time, when the run was published.

Task definition

- task: bcook.azdevops-testplan-extension.publishtestplanresults.PublishTestPlanResults@0
  displayName: 'Publish ObjectManagement (Container) test results'
  inputs:
    accessToken: '$(PublishTestPlanResultsAccessToken)'
    testPlan: 'HL_Master_Integration'
    testResultFormat: mstest
    testResultDirectory: '$(TargetTestResultsFolderLinux)/mstest'
    testResultFiles: ObjectManagementTests.trx
    testRunTitle: 'ObjectManagement (Container)'

Environment Details

We are using Azure DevOps Server 2022.2 (AzureDevopsServer_20250527.1)

• build-agent: self-hosted
• test-format: mstest/trx
• test-lanugage: C#
• pipeline-format: Designer-based (Classic)

Pipeline Output

This is the output without system.debug enabled. If you need it with system.debug enabled, please let me know.

2025-11-14T04:16:14.3827822Z ##[section]Starting: Publish ObjectManagement (Container) test results
2025-11-14T04:16:14.3837636Z ==============================================================================
2025-11-14T04:16:14.3838289Z Task         : Publish Test Plan Results
2025-11-14T04:16:14.3838544Z Description  : Publishes cross-platform test results (xUnit, JUnit, NUnit, Mocha, Cucumber) to an Azure DevOps Test Plan
2025-11-14T04:16:14.3838920Z Version      : 0.1.0
2025-11-14T04:16:14.3839101Z Author       : Bryan Cook
2025-11-14T04:16:14.3841088Z Help         : 
2025-11-14T04:16:14.3841307Z ==============================================================================
2025-11-14T04:16:15.6363865Z ##[section]Locating Test Plan details...
2025-11-14T04:16:18.8633396Z Using Test Plan: HL_Master_Integration
2025-11-14T04:16:28.7656892Z Available Test Points: 2006
2025-11-14T04:16:28.7658834Z ##[section]Reading test framework results...
2025-11-14T04:16:28.7707933Z Test format: mstest
2025-11-14T04:16:28.7709964Z Test files:
2025-11-14T04:16:28.7713018Z - /home/svc_prc_inttest/azagent/_work/_temp/TestResults/mstest/ObjectManagementTests.trx
2025-11-14T04:16:28.7849064Z Total: 14	Passed: 14	Failed: 0	Skipped: 0
2025-11-14T04:16:28.7869775Z ##[section]Mapping test framework results to Test Points...
2025-11-14T04:16:28.9095402Z 
2025-11-14T04:16:28.9096460Z Mapped 14 automated tests to test points:
2025-11-14T04:16:28.9107041Z | Test Point | Automated Test | TestOutcome |
2025-11-14T04:16:28.9108746Z |------------|----------------|-------------|
2025-11-14T04:16:28.9109852Z | 2109340 | Helpline.ObjectManagement.IntegrationTests.FormManagementTests.TC_324252_DeleteFormListItemInTheMiddle_TranslationsAreRepaired_Bug_319014 | 2 |
2025-11-14T04:16:28.9111261Z | 2123652 | Helpline.ObjectManagement.IntegrationTests.FormManagementTests.TC_405310_FormDefinition_CrossCheck_AllSourceTypes_AllAttributeTypes | 2 |
2025-11-14T04:16:28.9112730Z | 2117030 | Helpline.ObjectManagement.IntegrationTests.Tests.TemplateTests.TC_388326_MoveTemplateDefinition_FromGlobal_ToPersonal_OtherAgent_Fails | 2 |
2025-11-14T04:16:28.9114062Z | 2116914 | Helpline.ObjectManagement.IntegrationTests.Tests.TemplateTests.TC_385805_CreateUpdateReadTemplate_Personal_Root | 2 |
2025-11-14T04:16:28.9115257Z | 2117012 | Helpline.ObjectManagement.IntegrationTests.Tests.TemplateTests.TC_387971_CreateAndDeleteTemplateGroup | 2 |
2025-11-14T04:16:28.9116554Z | 2117029 | Helpline.ObjectManagement.IntegrationTests.Tests.TemplateTests.TC_388319_MoveTemplateDefinition_FromGlobal_ToPersonal_Success | 2 |
2025-11-14T04:16:28.9118058Z | 2117033 | Helpline.ObjectManagement.IntegrationTests.Tests.TemplateTests.TC_388562_CreateUpdateReadTemplateGroup_Personal_Root | 2 |
2025-11-14T04:16:28.9119318Z | 2118366 | Helpline.ObjectManagement.IntegrationTests.Tests.TemplateTests.TC_393556_ComplexText_WithEmbeddedImage | 2 |
2025-11-14T04:16:28.9120508Z | 2118720 | Helpline.ObjectManagement.IntegrationTests.Tests.DetailViewConfigurationTests.TC_396742_ImportExport_AllPermissions | 2 |
2025-11-14T04:16:28.9121675Z | 2118719 | Helpline.ObjectManagement.IntegrationTests.Tests.DetailViewConfigurationTests.TC_396743_ImportExport_OnlyPersonalPermission | 2 |
2025-11-14T04:16:28.9123060Z | 2118754 | Helpline.ObjectManagement.IntegrationTests.Tests.DetailViewConfigurationTests.TC_397504_GetCurrentDetailViewConfiguration_WithAllScopes_CrossCheck | 2 |
2025-11-14T04:16:28.9124369Z | 2118718 | Helpline.ObjectManagement.IntegrationTests.Tests.DetailViewConfigurationTests.TC_396746_Import_WithErrors | 2 |
2025-11-14T04:16:28.9125560Z | 2118755 | Helpline.ObjectManagement.IntegrationTests.Tests.DetailViewConfigurationTests.TC_397971_SaveConfiguration_AllTypes | 2 |
2025-11-14T04:16:28.9126857Z | 2114419 | Helpline.ObjectManagement.IntegrationTests.Tests.WorkflowTests.TC_370559_OnWorkflowInstanceTerminated_SetCaseClosed | 2 |
2025-11-14T04:16:28.9127788Z ##[section]Publishing TestResults ...
2025-11-14T04:16:30.1113994Z Publishing test results to test run '2402722'
2025-11-14T04:16:30.4247477Z Identified 14 test results with attachments.
2025-11-14T04:16:30.7117944Z Published Test Run: https://.../_TestManagement/Runs?runId=2402722&_a=runCharts
2025-11-14T04:16:34.9659839Z ##[section]Finishing: Publish ObjectManagement (Container) test results

Expected behaviour

The start time, end time and duration of each test in the run should match those in the trx file.

Screenshots

Here is a screenshot directly from the classic release pipeline showing a run published by your extension 'ObjectManagement (Container)' and one that is published via the VSTest task ('Shop').
On the right you see the Date started and Date completed of a particular test.

Here you can see what the trx file says about the particular test's start and end times and the duration:

[bryanbcook]

Originally, the design of this extension was to update the Test Plan and I wasn't planning to have this represent a drop-in replacement for PublishTestResults, though I understand you are primarily using this in a Release pipeline and you're relying on the published TestRuns for analysis. I agree adding the start + completed timestamps would be a good addition.

At the moment I am including the durationInMs, this would require the startedDate and completedDate to be included in the response when test results are published.

Unfortunately, the library that I'm using to read the cross platform results only includes the duration at the moment. There are existing issues in that project (85, 14) for missing timestamps. Those are aging issues because it isn't just TRX but many other test formats as well and not all formats include start + end timestamps.

I'll take a look at that project to see if we can get a partial fix.

[bryanbcook]

On the right you see the Date started and Date completed of a particular test.

@C0nquistadore This is from the build stage of a classic pipeline? In the meantime, does the TestRun expose the duration values you need?

[C0nquistadore]

This is from the build stage of a classic pipeline?

Correct. The tests tab of a particular stage of a classic release pipeline run:

In the meantime, does the TestRun expose the duration values you need?

Not sure what you mean, if I understand it correctly, the duration values you see on my first screenshot on the left are taken from the actual test run, and they are all zero. This is what it looks like if I open the dedicated test run:

I gotta add, I am not quite sure of the actual state of the extension since I always have to build it, version it and deploy it manually. So if you added this recently, I'll probably have to update it.

[bryanbcook]

I am surprised you're seeing this, as this was raised previously in #48 (Last November) and released in 0.1.16. My automated unit tests only include junit and xunit for that scenario, but I have some regression tests that exercise these mstest results. Screenshot of that TestRun shows the durations:

While I'm only including the duration of the test execution, you would need the started and completed to determine sequence, which is still a valid concern.

[bryanbcook]

Also, fwiw I've included the vsix as a zip on the last few releases so you shouldn't have to compile.

[C0nquistadore]

Also, fwiw I've included the vsix as a zip on the last few releases so you shouldn't have to compile.

Great, that definitely makes it easier. I had my colleage with collection admin rights update the extension using the vsix from the latest github release and will get back to you, to see if the test results contain durations, when our nightly tests have run tomorrow.

[C0nquistadore]

@bryanbcook The test run today looked better! The duration for each test now shows up. This helps a lot to detect sudden performance drops. To be honest, start and end time isn't that important to us at least for that matter.

[bryanbcook]

Glad to hear that it was just an out of date extension. I am aiming to get a 1.0.0 release in the marketplace by the end of the year.

I'll leave this issue open for now as I'm looking at the testparaer defects. Surprisingly, of the supported test frameworks only a small handful of them actually capture the start and end date for the test execution, so it might easy to address.