I've started thinking about this last year and wrote down some thoughts in this draft post: https://ttm.sh/2l3.md https://ttm.sh/2l3.md > Could we get the bes

I've started thinking about this last year and wrote down some thoughts in this draft post: https://ttm.sh/2l3.md https://ttm.sh/2l3.md > Could we get the best of both worlds by treating specification and compliance (testing) as a single problem? This hypothetical approach i call specification-driven development, whereby a specification document is intended both for human and machine consumption. In that case, the specification contains a written presentation of concepts, in addition to a machine-readable test suite that follows a certain format to programmatically ensure that the concepts and behavior described in the specification are implemented properly. I've centered the document on my personal usecases (CLI and sysadmin checks) but i don't see a reason it couldn't be employed for API/ABI checks.