Refactor TestResult and execution flow #7
Merged
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 change refactors the test execution and result reporting logic.
TestSuite.ExecuteAsyncmethod has been updated to return aTestResultobject directly, simplifying the flow inFUnit.RunAsync.TestResult.Testrecord has been changed to support multiple errors by using anIReadOnlyList<Error>?instead of a singleError?.SkippedTestsproperty has been removed fromTestResult. Skipped tests are now determined by checking ifExecutionCountis 0, as per the new logic.TestSuite.ExecuteAsync, andTestResultnow containsTotalExecutionTime.FUnit.RunAsynchas been updated to safely get the first error usingFirstOrDefault()and to no longer log the stack trace.PR created automatically by Jules for task 15002481801996859869