Posts Tagged ‘testability’
A LinkedIn forum question resonated with a question that has long interested me.
“The UML comprises 13 diagram types, the SysML comprises 9 diagram types. Each of these offers a different view of a planned system and helps to create a common understanding. But how many diagrams are necessary, and how many…
Read More
Technical debt refers to aspects of a codebase are incomplete, deficient, obsolete, or buggy. This can occur for many reasons: insufficient time, uncertainty, omissions, poor workmanship, or poor management. This is termed “debt” because it will take additional time and money to correct, update, or revise.
Technical equity refers to aspects of a…
What makes a software system easier or harder to test?
The general aspects are controllability and observability.
This post covers part two of my 2010 talk on testability.
Controllability determines the work it takes to set up and run test cases and the extent to which individual functions and features of the system under test…
My 2010 keynote at the Google Test Automation conference considered the dimensions of software testability and its implications.
Click here for the slides.
Click here to view the video
This presentation is serialized in following posts.
Part 1: Testability: What is it?
Part 2: Controllability and Observability
Part 3: Accidental Untestability
Part 4: White Box Testability
Part 5:…
Bob Binder on 
APN on 
Sy on 
henda farhani on 
J on