bazelbuild / bazelbuild/rules_apple
Option to use build_for_testing to prepare UITests builds
- Dominant language
- Starlark
- Stars
- 593
- Forks
- 334
- Avg merge
- 16h 48m
- Merged PRs (30d)
- 9
Description
Is there any option to build `*Test-Runner.app` for `ios_ui_test` target for device? Currently when trying to build `ios_ui_test` target as a result you will get `*.ipa` file of main application + `*Tests.zip` archive containing only `*Tests.xctest` file.
There is an option to get `*Test-Runner.app` using xcodeproj generated with `rules_xcodeproj`. When building test target with Xcode for testing or using `xcodebuild build_for_testing` `*Test-Runner.app` is actually built. But there is a problem that it is building always for simulator. Test target generated with `rules_xcodeproj` supports only simulator. When building it is always creating `*Test-Runner.app` for simulator even when main app target is built for device.
Contributor guide
Research direction
Start by comparing the ios_ui_test build output with Xcode's build_for_testing behavior and the rules_xcodeproj-generated test target. Done means a device build produces the *Test-Runner.app alongside the application IPA and test archive, rather than only a simulator runner.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios
- Domain
- build-system, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100