Add macOS tests (Part 1)#45644
Conversation
c7619ce to
71fc3bd
Compare
71fc3bd to
a4931cb
Compare
247eec7 to
4cedd37
Compare
4cedd37 to
972bdc2
Compare
b9900ce to
0958510
Compare
shihaohong
left a comment
There was a problem hiding this comment.
I'm not 100% done with reviewing this yet, but I want to comment quickly about a few things I have to note before continuing:
-
It might be tough to tell from the beginning whether or not the test applies to a particular platform or not if a developer is not expecting the
variantproperty at the end of the test without having something like (iOS) or (Android) in the test name. I feel like where possible, it might be better to just leave in the target platforms in the test names to avoid confusion when interpreting a unit test. -
We should also probably rename this PR to something like
Test refactorand list out potential changes in the description of the PR. It's not entirely accurate that it's just adding macOS tests -- this PR adds additional testing for Fuchsia in some parts, since Fuchsia was added as a target if I'm understanding the code correctly, and reintroduces some tests that work correctly now but were originally commented out due to bugs. -
Wouldn't it be better to separate these changes out into multiple PRs? I'm not very confident that I caught every case where something could have been accidentally altered or if the tests are correct since this PR touches many different types of tests. Looking through the PR, I am simply pattern-matching what the test used to test for and assuming the same pattern would apply to macOS correctly.
0958510 to
5d77362
Compare
|
Excellent point about breaking this up. I'm going to break this up into several different changes so they can be reviewed separately. |
8527d53 to
bc3171b
Compare
bc3171b to
a988329
Compare
…nd services libraries.
a988329 to
e896499
Compare
Description
This contains the test changes for adding
TargetPlatform.macOS, which was done in #43457.The main goal of this PR is to enable tests that are currently running only on iOS to also run on macOS, but only for the tests where that makes sense. For instance, we don't run any of the haptic feedback tests on macOS.
Related Issues
Tests
Breaking Change