liveBook · Manning

End-to-end testing

As explained in Think Like a Software Engineering Manager

End-to-end testing evaluates an entire application or system through behavior that represents real-world use.

End-to-end testing checks an entire application by simulating real-world production functionality, validating behavior across the system rather than within one isolated component. section 12.2.2

Use end-to-end testing with clear trade-offs:

  • It validates the system as a whole across the extensive codebase. section 12.2.2
  • It runs more slowly and costs more to maintain than other testing approaches. section 12.2.2

How Think Like a Software Engineering Manager covers it

How deep it goes
Examines whole-application behavior but stops short of implementation guidance, test design steps, or tool details.
Examples
Simulates real-world production functionality and appears as the top layer of the test automation pyramid.
What you can do after
Evaluate whether an application behaves correctly as a complete system, while recognizing its slower pace and higher maintenance cost.
How it connects
Contrasts with unit testing, integration testing, load testing, performance testing, and regression testing.

Also explained in

Compare how 12 books explain end-to-end testing →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.