A Mini Program runs inside a host application, so its automation surface may differ from an ordinary native screen or browser page. The first task is to discover what the supported developer tools and the target device actually expose.
Separate the layers
Do not assume every Mini Program is a switchable WebView or that an arbitrary third-party Appium driver supports the current WeChat release. Start with the official Mini Program tooling, record the supported versions, and prove one small scenario before expanding coverage.
Make a representative experiment
- Launch the intended test build and enter the Mini Program through a repeatable host flow.
- Verify one read and one interaction through the documented automation surface.
- Check navigation back to the host and restoration of the test account state.
- Measure launch and interaction behavior on the supported device matrix.
- Repeat the experiment when the host or developer tools change.
When a surface is unavailable, record the limitation and place coverage at another layer, such as the service contract or a manual device check. A brittle coordinate sequence can be a bounded fallback for a stable screen, but it should not be mistaken for semantic access to internal elements.
