Book
Full Stack Testing
A Practical Guide for Delivering High Quality Software
Gayathri Mohan
Summary
A survey of the testing skills that sit outside the usual unit-and-integration conversation: exploratory testing, cross-functional requirements, data, visual, security, performance, accessibility, and mobile, closing with a chapter on testing newer technologies such as AI-based systems. The premise is that a delivery team is now expected to cover all of them while most engineers have real depth in only one or two. Each area gets its concepts, the tools currently used for it, and where it belongs in a CI/CD pipeline. Read as a map of the territory it is genuinely useful — it is good at showing you what you are not testing. It is deliberately not a deep treatment of any single technique, so expect to go elsewhere once an area turns out to matter to you.
Target Readers
- Test leads and QA engineers who want a checklist of the quality dimensions their pipeline does not yet cover
- Developers comfortable with unit and integration testing who need an orientation to performance, security, and accessibility testing before choosing where to go deeper
Tags
Colophon
- Publisher
- Shoeisha
- ISBN
- 978-4798190471
- Published
- Jul 2025
- List price
- ¥4,620incl. taxMay differ from the actual selling price on Amazon
Get this book
* The link above is an advertisement via Amazon Associates.Related Books
Prerequisites
- Recommended
Unit Testing Principles, Practices, and Patterns
Vladimir Khorikov
Reason: Once unit tests form a solid base, you stack integration, contract, and end-to-end tests in the right proportions along the test pyramid, scaling up to a system-wide quality strategy. The rule is many at the bottom, few at the top.
- Related
Testing JavaScript Applications
Lucas da Costa
Reason: Once you've established a JavaScript testing strategy, you broaden your view beyond the frontend to whole-system quality optimization including CI/CD. Full Stack Testing provides a quality strategy spanning contract, performance, security, and E2E, positioning testing as part of development culture.
- Related
Property-Based Testing with PropEr, Erlang, and Elixir
Find Bugs Before Your Users Do
Fred Hebert
Reason: Once you can verify invariants, you place that skill within a quality strategy spanning unit, integration, and end-to-end. You design what property each layer guarantees, giving the whole pyramid coherence.
Next Books
- Recommended
Accelerate
The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations
Nicole Forsgren, Jez Humble, Gene Kim
Reason: Once testing and CI/CD give you a foundation for building in quality, you frame how it affects organizational delivery performance through measurement. DORA's four key metrics show empirically that speed and stability are not a trade-off.
- Related
Leading Quality
How Great Leaders Deliver High Quality Software and Accelerate Growth
Ronald Cummings-John, Owais Peer
Reason: Once you have a technical quality strategy in hand, you widen your view to how to embed it at the team and organizational level. The subject shifts from the quantity and kinds of tests to decision-making and culture around quality.