You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have best effort support for iPad devices. We should add some testing to our e2e suite.
Notes on Open MCT Mobile
The biggest difference between the ipad suite is the lack of a create button.
The most important displays or domain objects to focus on will be
notebooks
plots
Mobile-specific things to test
The mobile-specific things we will need to test:
"mobile touch" works with interactive elements like the search bar
screen orientation changes
Execution
In no particular order:
Determine the exact iPad devices which will be used during the mission. Update our project in playwright-*.config.js
Update existing test suites which do not need domain objects (like timeConductor) to support
Add a new test suite which tests mobile-specific things like screen orientation change
Investigate a visual testing suite. It's possible that percy's DOMSnapshot publishing would override the mobile view.
Update our CI such that this only runs once per platform. Since this is an emulator/simulator, there's no reason to test this on macOS, Windows, and Ubuntu
Run the iPad view on the nightly with at least one test suite (smoke)
The text was updated successfully, but these errors were encountered:
Summary
We have best effort support for iPad devices. We should add some testing to our e2e suite.
Notes on Open MCT Mobile
The biggest difference between the ipad suite is the lack of a create button.
The most important displays or domain objects to focus on will be
Mobile-specific things to test
The mobile-specific things we will need to test:
Execution
In no particular order:
project
inplaywright-*.config.js
The text was updated successfully, but these errors were encountered: