liveBook · Manning

User testing

As explained in Lead Developer Career Guide

A technique that evaluates software by observing representative users interact with it.

User testing evaluates software by observing end users interact with a prototype or early version. It reveals usability and functionality problems through direct interaction. section 8.1.3

Choose user testing when you need to:

  • Observe how representative users actually interact with unfinished software. section 8.1.3
  • Gather feedback on whether the software is usable and functionally appropriate. section 8.1.3
  • Compare direct user needs with client requests, especially when technical preferences risk over-engineering the product. section 8.1.3

A practical contrast

A technically skilled client may request complex software that nontechnical users struggle to understand. Observing those users interact with an early version can expose the gap between the requested solution and the needed experience. section 8.1.3

How Lead Developer Career Guide covers it

How deep it goes
Defines the observation-based method and its purpose, but does not specify a testing procedure or analysis framework.
Examples
Uses prototype interaction and a B2B mismatch between technical client requests and nontechnical user needs.
What you can do after
Evaluate software usability and functionality through observed interaction with end users.
How it connects
Contrasts user testing with interviews, focus groups, surveys, and heatmaps as alternative ways to gather user insight.

Also explained in

Compare how 3 books explain user testing →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Lead Developer Career Guide. The section links point to the parts of the book it draws on.