[CI] Use dotnet-test-slicer in nightly tests #8154
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.
Updates the
TimeZoneInfo
andLocalization
test stages to use thedotnet-test-slicer
tool used by other MSBuild test runs.These test jobs have a pretty high frequency of failing and timing out,
and a few changes have been made to try to reduce the points of failure.
SetUp and TearDown functions have been trimmed down and made standard
across the two fixtures. OneTimeSetup will prepare the device and
install the project, and we will only attempt to attach log files during
TearDown.
The tests will launch the app activity directly with ADB, rather than
using
dotnet build -t:Run
for every iteration. The tests will attemptto reinstall the app if it is not present as a fallback.