feat: Add startTime+endTime timestamps to test case results #108
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
original obtained from: https://nunit.org/files/testresult_30.txt Differences - Test Cases marked as "Invalid" are represented in the sample as Failed instead of Skipped. - Test Suites marked as "Invalid" are represented in the sample as Failed instead of Skipped. - Ignored and BadFixtures in the sample do not have test-case elements though the suite reports total test case values greater than zero. The nunit3-console includes the test-case elements so the number of total tests and ignored tests is higher.
Contributor
Author
|
@ASaiAnudeep thoughts? |
ASaiAnudeep
reviewed
Nov 26, 2025
bryanbcook
changed the title
Contributor
Author
|
Good to merge? I have a few additional PRs to merge based on these commits. |
bryanbcook
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces
startTime+endTimetimestamps to individualTestCaseresults, which is similar to #16. Having timestamps at this level allows analysis to establish the sequence of test execution.Based on research, only MSTest, NUnit and TestNg have direct support in their schema for this. Other implementations will have an undefined value for
startTime+endTime.As this introduced new properties to the model objects, all brittle tests were impacted. Related to #93, I reworked the xunit, mstest, nunit and testng tests to use explicit assertions for their specific test concerns; roughly 16 of the 40 impacted tests were addressed. Reducing this friction will make introducing #85 easier, and address issue #93
Related to nunit_v3.xml, which was originally sourced from https://nunit.org/files/testresult_30.txt, I noticed timestamps were missing so I recreated the output using nunit3-console.exe. There were significant differences from the sample: