wordpress-mobile / wordpress-mobile/WordPress-Android
Re-add Block Editor e2e test
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 3.2k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 69
Description
Previously we had an e2e test for opening the Block Editor and then switching to the classic editor, that test was disabled because of performance constraints.
The Block Editor has had some performance improvements since that test had @Ignore key word added, it may be a good time to revisit adding a simple Block Editor test to the WPAndroid e2e test suite for catching issues related to Gutenberg editor code version mismatches or other issues with the Block Editor.
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
Review WordPress/src/androidTest/java/org/wordpress/android/e2e/BlockEditorTests.java, especially the previously disabled test around lines 37-73. Check whether the Block Editor can now be exercised within the e2e suite without the earlier performance constraints. Done means a simple Block Editor test is active and catches editor version mismatches or related Block Editor issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100