wordpress-mobile / wordpress-mobile/WordPress-iOS
Classic Editor tests disabled until we update to edit existing classic post
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 3.9k
- Forks
- 1.2k
- Avg merge
- 23h 51m
- Merged PRs (30d)
- 58
Description
Summary
The Classic (Aztec) editor is being deprecated for creating new posts in WPiOS. See simple sites classic editor deprecation for new posts PR here: https://github.com/wordpress-mobile/WordPress-iOS/pull/15766. Atomic, and self-hosted blogs are planned to happen afterwards.
Since users will still be able to edit existing posts, existing classic editor tests should be updated to edit an existing classic post, instead of creating a new one.
While this work is pending, classic editor tests are disabled.
Update: We decided in p9ugOq-20E-p2#comment-4395 to re-enable the classic tests to help prevent any future classic editor regressions. We'll only re-enable the simplest test, testTextPostPublish, since we only want a minimal test in place.
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 with WordPress/WordPressUITests/Tests/EditorAztecTests.swift and inspect the disabled Classic editor tests, especially testTextPostPublish. Update the selected test to edit an existing classic post rather than create a new one, then re-enable only that simplest test and run the Classic editor UI tests to verify it passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- mobile, testing-qa
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100