Open
Bug 1420125
Opened 7 years ago
Updated 2 years ago
XCUITests - FxScreenGraph: navigation.back() does not work on iPad on some situations
Categories
(Firefox for iOS :: Build & Test, defect, P3)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
fxios | + | --- |
People
(Reporter: isabel_rios, Unassigned)
Details
Attachments
(1 file)
17.76 KB,
image/png
|
Details |
So far it has been detected when trying to go back from one of these screens: set passcode, change passcode, enter passcode
Reporter | ||
Updated•7 years ago
|
Summary: XCUITests - FxScreenGraph: navigation.back() does not on iPad on some situations → XCUITests - FxScreenGraph: navigation.back() does not work on iPad on some situations
Comment 1•7 years ago
|
||
typePasscode sometimes fails because the Soft Keyboard is not available. This does not seem to be available programatically.
Comment 2•7 years ago
|
||
typePasscode sometimes fails because the Soft Keyboard on the simulator has been toggled off. Setting this correctly does not seem to be possible from within the test. Are there any more concrete STR?
Updated•7 years ago
|
Reporter | ||
Comment 3•7 years ago
|
||
There are a few examples in Authentication.swift test suite: https://github.com/mozilla-mobile/firefox-ios/blob/master/XCUITests/AuthenticationTest.swift For example: -Test in L190: https://github.com/mozilla-mobile/firefox-ios/blob/master/XCUITests/AuthenticationTest.swift#L190 We type an incorrect passcode and want to go back to Passcode Settings screen, we can only do that on iPad by tapping on Cancel -Test in L215: https://github.com/mozilla-mobile/firefox-ios/blob/master/XCUITests/AuthenticationTest.swift#L215 We try to change the passcode by typing an incorrect one, an error message is shown and we want to go back to Passcode Settings screen So far these are the example I found, only with that Set passcode, change passcode or enter passcode screen. If I find more, will add them here. Thanks!
Flags: needinfo?(irios.mozilla)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•