gmgauthier/work-blog
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(articles): refine wording in testing-telos article

Browse Source 
Add a sentence to better introduce the concept of testing strategies as shapes, improving clarity and flow in the paragraph.
This commit is contained in:
Gregory Gauthier 2026-04-17 12:41:49 +01:00
parent 7b1428ee55
commit f5a88637e6
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
articles/published/testing-telos.md
View File

@ -2,7 +2,7 @@
The classic *Testing Pyramid* is not wrong; it is simply *incomplete*. It was forged for one specific kind of engineering work: the steady addition of new user-facing features. In that narrow context the pyramid makes perfect sense: a broad base of fast, inexpensive unit tests, a smaller middle layer of integration tests, and a thin apex of end-to-end checks. The shape itself is the visual signature of a final cause or ultimate purpose of that work. The word that Aristotle used for this concept, was *telos*.
Software engineering is not a single kind of work. Different engineering goals demand different testing strategies. The famous pyramid is only one of four natural shapes that emerge when we observe what teams actually *do* in practice. Each shape is the visible expression of a distinct *telos*.
Software engineering is not a single kind of work. Different engineering goals demand different testing strategies. We can conceptualise these strategies as simple shapes. The famous pyramid is one such shape, and only one of four natural shapes that emerge when we observe what teams actually *do* in practice. Each shape is the visible expression of a distinct *telos*.
In Aristotelian terms, software testing (and software development) is *techne* — a craft. A craftsman does not begin with a fixed form and force every material into it. He begins with the *purpose* the artifact must serve, then lets the material and the method follow. In testing, the software is the material object; the testing strategy is the form; and the engineering goal is the telos. When these causes are mismatched, confidence is illusory and effort is wasted.