Better unit tests for ios/android
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 258
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
Recently it became clear that the ios/android builds were broken due to clang++-3.8 being installed for those platforms (and not being available). Glitches that cascade from the main .travis.yml need to be caught by unit tests somehow and this ticket will track this. Independently we could remove cascading to avoid this particularly breakage, but the issue still remains that we should be testing ios/android (and other achs?) better.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the main .travis.yml and the existing iOS/Android build and unit-test setup first. Reproduce or trace how the clang++-3.8 configuration cascades to those platforms, then add coverage that detects unavailable compiler settings and catches broken iOS/Android builds. Done means the relevant platform checks fail clearly instead of silently inheriting a broken configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, cpp, ios
- Domain
- build-system, ci-cd, mobile, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100