Today this is the second post I see where the 'traditional' testing methods (unit, e2e, integration, perf, pen, etc) are re-categorized, are put in new perspectives.
The other one is https://alperenkeles.com/posts/vocab-for-testing/
I truly understand our (only) job is to become the oracles of the machine: https://www.osequi.com/manifesto
Not sure I’m following, are you implying that deterministic simulation testing is a just a new name for a “traditional” test method? I’m not clear because 1. Deterministic simulation testing is not a new concept. (Foundation DB is one of the poster boys for it) 2. All the test methodologies mentioned are a name for a specific pattern and practice of testing, and DST is the same thing.
I'm betting on something adjacent but flipped. As agents are writing the code, humans are stopping (and getting worse at) reviewing, so the oracle needs to be mechanical. My personal bet: https://github.com/NMitchem/charpente/blob/main/MANIFESTO.md