Log In
Or create an account -> 
Imperial Library
  • Home
  • About
  • News
  • Upload
  • Forum
  • Help
  • Login/SignUp

Index
Title Page Table of Contents Introduction Generating test ideas Define a shared big-picture view of quality Explore capabilities, not features Start with always/never Tap into your emotions Test benefit as well as implementation Quantify even if you cannot measure Organise test ideas using an ACC matrix Use risk checklists for cross-cutting concerns Document trust boundaries Monitor trends in logs and consoles Mob your test sessions Don’t let the pen be the bottleneck Snoop on the competition Designing good checks Focus on key examples Contrast examples with counter-examples Describe what, not how Avoid mathematical formulas Flip equivalence classes between inputs and outputs Clearly separate inputs and outputs Ask ‘what happens instead?’ Use Given-When-Then in a strict sequence One test, one topic Treat too many boundaries as a modelling problem Prefer smaller tables Balance three competing forces Write assertions first Split technical and business checks Don’t automate manual tests Improving testability Wrap synchronous database tests in transactions Set up before asynchronous data tests, don’t clean up after Introduce business time Provide atomic external resources Wait for events, not time Split data generators from tests Minimise UI interactions Separate decisions, workflows and technical interactions Use production metrics for expensive tests Managing large test suites Make developers responsible for checking Design tests together with other teams Avoid organising tests by work items Version control tests along with software Create a gallery of examples for automation patterns Decouple coverage from purpose Avoid having strict coverage targets Measure your tests’ half-life Optimise for reading, not writing Name tests for search engine optimisation Explain the purpose of a test in the introduction Split just-in-case tests from key examples Let the chaos monkey out periodically The End Authors Bibliography and resources Legal Stuff
  • ← Prev
  • Back
  • Next →
  • ← Prev
  • Back
  • Next →

Chief Librarian: Las Zenow <zenow@riseup.net>
Fork the source code from gitlab.

This is a mirror of the Tor onion service:
http://kx5thpx2olielkihfyo4jgjqfb7zx7wxr3sd4xzt26ochei4m6f7tayd.onion