Given that test ids are constant across test runs, we can uniquely identify test ids so we can only render the newest result for a given test (see https://github.com/microsoft/testfx/issues/1149).
This means that if you re-run dotnet test (potentially with some filters to only re-run failed tests, say), even if you end up with multiple test result files, you would get the expected render which would be the aggregated results across multiple runs, with the latest present status being the one which wins.
This also means we can get a unified summary of an entire solution folder when running multiple test projects in a solution (which would end up generating multiple results files).
Given that test ids are constant across test runs, we can uniquely identify test ids so we can only render the newest result for a given test (see https://github.com/microsoft/testfx/issues/1149).
This means that if you re-run
dotnet test(potentially with some filters to only re-run failed tests, say), even if you end up with multiple test result files, you would get the expected render which would be the aggregated results across multiple runs, with the latest present status being the one which wins.This also means we can get a unified summary of an entire solution folder when running multiple test projects in a solution (which would end up generating multiple results files).