Just asking for my own learning, why do our Android tests not need any of the code in these (rather large) blocks?

On the emulator, clicking add image doesn't add an image to the image block, so that's why when running the test on iOS (Add Image > WordPress media library) it actually adds an image but on Android it doesn't. 🤔 I could probably move this code into a function to make it a little less obvious, WDYT?

Thanks for explaining! That makes sense.

I do think it would be helpful to add a bit more context where we're doing these !isAndroid() checks. I don't have any strong preference between just adding a comment versus moving this code into a function, or even just creating a local "alias" along the lines of isCapableOfAddingImageToImageBlock() = () => ! isAndroid();, which would then be pretty descriptive if we used it in place of the !isAndroid() checks. Whatever you think would work best is fine with me.

I just opted for more context in the comments

Certainly not something that needs to be changed, but FWIW in code like this I generally find it nice to separate out the things that vary (the path) from the things that don't (method call).

const path = isAndroid() ? 
        '//android.view.ViewGroup[@content-desc="Post title. Welcome to Gutenberg!"]/android.widget.EditText' ) : 
        '//XCUIElementTypeOther[@name="Add title"]/XCUIElementTypeTextView' );
return await this.driver.elementByXPath(path);

Ahh you're right I I usually go with that approach, thanks I can change this