Keyboard

device.keyboard switches the on-screen keyboard between software (it shows, the default) and hardware (it stays hidden, as with a connected keyboard), live, so a spec can check a bottom sheet or a sticky footer riding it up and down.

import { expect, test } from "@delacour/warden-e2e";

test("the footer stays above the keyboard", async ({ app, device, screen }) => {
	await app.open();
	await screen.getByTestId("open-sheet").tap();
	await screen.getByTestId("sheet-input").fill("buy milk");
	await expect(device).toHaveKeyboard();
	await expect(screen.getByTestId("sheet-save")).toBeVisible();

	await device.keyboard("hardware");
	await expect(device).not.toHaveKeyboard();
});

device.hideKeyboard() dismisses a keyboard that is up: iOS resigns the first responder through the injected library (never Return, so no form is submitted; an app running without the library falls back to Enter), Android presses back.

On iOS, a tap on a target the keyboard covers first scrolls it into view or dismisses the keyboard, then taps. On Android, call device.hideKeyboard() first.

The mode goes back to the suite's conditions.keyboard (else software) when the test ends.

Typing aids are off

On an iOS Simulator, warden turns off autocorrect, predictive text and spell check (com.apple.keyboard.preferences) when it starts driving the device, so text a spec types reads back exactly as typed. Without this, a fresh simulator can rewrite a word as the next space goes in (Buy + milk read back as But milk). Autocapitalization stays on. The settings stay on the simulator.

In a suite

conditions: { keyboard: "hardware" },

Applied at the start of each spec and put back when it ends. Values: "software" or "hardware".

How each platform switches it and warden ui keyboard: Keyboard on a simulator.