Increase mobile app E2E test robustness #55251
Labels
Mobile App - i.e. Android or iOS
Native mobile impl of the block editor. (Note: used in scripts, ping mobile folks to change)
[Type] Automated Testing
Testing infrastructure changes impacting the execution of end-to-end (E2E) and/or unit tests.
[Type] Enhancement
A suggestion for improvement.
[Type] Tracking Issue
Tactical breakdown of efforts across the codebase and/or tied to Overview issues.
What problem does this address?
In addition to other test types, we rely upon E2E tests for critical flows related to native OS features. The current native mobile editor E2E tests provide a good foundation for our needs. However, there is opportunity to increase the tooling robustness, refactor to make it more approachable, and remove dead code/unused abstractions now that we prioritize integration tests.
What is your proposed solution?
We could work on the following tasks to improve the robustness and approachability of the E2E tests.
npm install
- test: Improve E2E test consistency #55554device-tests:local
command to launch the Android emulator via theemulator
CLI. #55567EditorPage
andutils
to support applying changes in watch modeThe text was updated successfully, but these errors were encountered: