assertWithMatcher:matcherForSufficientlyVisible if Connect Hardware Keyboard is disabled

[raynor85]

Description

On iphone simulators, if Connect Hardware Keyboard is disabled, elements retrieved by id, labels or in other methods fail the toBeVisible expectation throwing:

"Assertion Criteria" : "assertWithMatcher:matcherForSufficientlyVisible(>=0.750000)"

The reason why it should work even if that settings is disabled is because the user might want to use the methods typeText and clearText in his tests (which they both breaks if this settings is enabled). I think using replaceText is a dirty workaround.

Steps to Reproduce

Just run a test having toBeVisible expectation on any iPhone simulators having that settings off in a React Native project (mine is 0.46.4).
If you run the same test with Connect Hardware Keyboard enabled, it passes.

• Node: v8.2.1
• Device: iPhone 6
• Xcode: 8.3.3
• macOS: Sierra 10.12.6

[LeoNatan]

Are you sure your element is not hidden behind the keyboard? When hardware keyboard is connected, the software keyboard usually does not show up, creating a state that is unnatural for users—you can type but the software keyboard is hidden. Often, people developing on the simulator forget this part and don’t optimize their app properly for the software keyboard.

[LeoNatan]

Hello,

We are moving support questions to Stack Overflow. Please ask a question there with the detox tag. This section is only meant for Detox issues and enhancement requests.

Thanks