Ensure the CI is marked as failed when Maestro test is failing (#4700)
* Ensure the CI is marked as failed when Maestro test is failing * Fix typo in String to disable bookmark in ChromeCustomTab * Fix Maestro test now that matrix.org is using MAS to authenticate. * Fix Maestro test - other issues due to recent changes. * Maestro: add test on Element Call * Run through Chrome on boarding step. * Try suggestion from https://github.com/mobile-dev-inc/Maestro/issues/1126#issuecomment-2842220361 * Revert "Try suggestion from https://github.com/mobile-dev-inc/Maestro/issues/1126#issuecomment-2842220361" This reverts commit d400644622c1a240deb61040f9095e3221e07f21. * Add comment on Maestro flow.
This commit is contained in:
parent
98cfddce3f
commit
318f72a78d
7 changed files with 36 additions and 13 deletions
|
|
@ -7,8 +7,9 @@ appId: ${MAESTRO_APP_ID}
|
|||
- tapOn:
|
||||
text: ${MAESTRO_INVITEE1_MXID}
|
||||
index: 1
|
||||
- tapOn: "Send invite"
|
||||
- takeScreenshot: build/maestro/330-createAndDeleteDM
|
||||
- tapOn: "maestroelement2"
|
||||
- scroll
|
||||
- tapOn: "Leave conversation"
|
||||
- tapOn: "Leave room"
|
||||
- tapOn: "Leave"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue