liveBook · Manning

User-interaction testing

User-interaction testing evaluates software behavior by exercising its user interface and observing resulting outputs, state changes, and interactions.

How 2 Manning books explain it

Django in Action

UI testing evaluates software by interacting with its user interface, often through tools that simulate user actions.

How it is used
Evaluates user-facing behavior by simulating actions through a browser-based interface.
How deep it goes
Explains browser round trips and Django server requirements, but defers comprehensive Selenium instruction.
Examples
Uses shipping-cost forms, browser-entered addresses, Selenium selectors, and Django live-server test classes.
What you can do after
Apply it via Selenium and Django live-server test classes to verify browser-visible behavior.

Read how Django in Action explains user-interaction testing →

BDD in Action, Second Edition

A UI test verifies software behavior through its user interface rather than through internal program interfaces.

How it is used
Verifies user journeys, visible UI behavior, and end-to-end component interactions within automated acceptance testing.
How deep it goes
Explains benefits, trade-offs, tool choices, testability hooks, and waits, while deferring most business-rule coverage to non-UI tests.
Examples
Uses browser-based user journeys, stakeholder demonstrations, screenshots, element identifiers, and explicit or fluent wait conditions.
What you can do after
Apply UI acceptance testing through Selenium WebDriver while selecting faster non-UI tests for rules and calculations.

Read how BDD in Action, Second Edition explains user-interaction testing →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.