This was also my first thought when reading OP. It is not restricted to testing even. The whole development process has this distinction (e.g. functional vs non-functional requirements) and it hurts more than it helps.
I think this is an important distinction that is also real when thinking about verification: verifying function can be boolean or lets say limited to a simple set while verifying non functional properties means mapping to a more continous interval and so it is a qualitative decision.
I dont think this will last much longer. Looking around, i see most engineers not being interested in anything other than AI related stuff. Certainly true for the junior ones
I would like "non-functional testing" to be called "cross-functional testing".
I think the alleged dictum between functional and non-functional is the biggest conceptual, theoretical, or even philosophical issue.
This was also my first thought when reading OP. It is not restricted to testing even. The whole development process has this distinction (e.g. functional vs non-functional requirements) and it hurts more than it helps.
I think this is an important distinction that is also real when thinking about verification: verifying function can be boolean or lets say limited to a simple set while verifying non functional properties means mapping to a more continous interval and so it is a qualitative decision.
[delayed]
I recall finding different definitions in every book about testing I read.
I think most of the confusion came from people suddenly deciding that a unit test can't test less than a whole object, in OOP.
Mad Men meme:
"Testing, but applied to terminology across publications."
Always enjoyable for us aged s/w engineers to see the new generations relearn the fundamentals.
I dont think this will last much longer. Looking around, i see most engineers not being interested in anything other than AI related stuff. Certainly true for the junior ones
AI opens up whole new ways of validating that systems behave correctly or to find issues.