wordpress-mobile / wordpress-mobile/AztecEditor-iOS
Tests: Add or update UI tests for more real world scenarios
Open
Nobody has claimed this yet.
[Type] Automated Testing
- Dominant language
- Swift
- Stars
- 669
- Forks
- 153
- Avg merge
- 11h 27m
- Merged PRs (30d)
- 4
Description
The existing UI tests have a couple downsides:
- They use numbers instead of strings due to autocorrect/autocomplete issues. We should disable that behavior in the test environment so we can use real strings.
- The tests don't have a mix of formatted and unformatted text. Ideally they would be more like the Android tests, which enter unformatted text first and then enter text with the selected formatting.
We should update our existing UI tests (or add to them, but I don't see a reason to keep the current ones as-is) to address these two issues.
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
Start by locating the existing UI tests and compare their scenarios with the Android tests referenced in the issue. Check how the test environment handles autocorrect or autocomplete, then update or extend the UI coverage for unformatted text followed by formatted text and verify both real-string input and formatting behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile-dev, testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100