[tests] Print labels after each MSBuild test when running from the command line. #14428
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
…mmand line. The advantage of writing the label after each test is that the test result will also be printed, which means it's possible to see if any tests failed during the test run, as opposed to having to wait until the entire test run is completed (which can take a while) to realize that pretty much every test failed with some silly mistake which could have been quickly fixed before re-running the tests.
Collaborator
Collaborator
❌ [CI Build] Tests failed on VSTS: simulator tests iOS ❌Tests failed on VSTS: simulator tests iOS. Test results1 tests failed, 104 tests passed.Failed tests
Pipeline on Agent XAMBOT-1017.Monterey |
dalexsoto
approved these changes
Mar 16, 2022
tj-devel709
approved these changes
Mar 16, 2022
Member
Author
|
Test failure is unrelated (https://github.com/xamarin/maccore/issues/2557). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
The advantage of writing the label after each test is that the test result will also
be printed, which means it's possible to see if any tests failed during the test
run, as opposed to having to wait until the entire test run is completed (which can
take a while) to realize that pretty much every test failed with some silly mistake
which could have been quickly fixed before re-running the tests.