CI *may* not be running all iOS UI tests #19617
Labels
area/tests 🧪
Categorizes an issue or PR as relevant to tests
difficulty/tbd
Categorizes an issue for which the difficulty level needs to be defined.
kind/bug
Something isn't working
platform/ios 🍎
Categorizes an issue or PR as relevant to the iOS platform
triage/untriaged
Indicates an issue requires triaging or verification
Comments
Youssef1313
added
difficulty/tbd
|
Yes, this is expected at this time. A tentative fix was implemented here: #6605, but never ended up finished. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current behavior
The test filter calculation (starting from this line)
uno/build/test-scripts/ios-uitest-run.sh
Line 23 in d04684e
is hardcoding namespaces. It's very possible that a developer accidentally introduce a new namespace that ends up not being tested in CI. Whether or not there is currently such untested tests is something I don't know.
Expected behavior
It may be better to follow the logic from Android where the generator is adding a bucket property and that's what will be used for filtering
How to reproduce it (as minimally and precisely as possible)
No response
Workaround
No response
Works on UWP/WinUI
None
Environment
No response
NuGet package version(s)
No response
Affected platforms
No response
IDE
No response
IDE version
No response
Relevant plugins
No response
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: