What is skill testing?

Question

Software testing

Guys, do not judge for a stupid question
What is ility testing?
Google, on this request, gives out only Non-functional testing, but even doubts torment me

Answer 1

Google, in this case, as almost always, is right)) We are talking about the so-called. non-functional requirements, i.e. those that cannot be taken like this, tested with a test, and made sure that "it works as ordered." This is the essence of the requirements of a qualitative nature, imposed on the architecture as a whole, or on separate groups of functional and / or system requirements. For example: "horizontal scaling of the data warehouse should not affect the system response time for registering new and deleting previously registered users", or, "the system should be portable to a 64-bit architecture with minimal costs"... or even cooler: "developed the system should make it easy for new developers to maintain the code."
The term "Ility" comes from the (now obsolete) ISO/IEC-9126, which has grown into a whole family of ISO/IEC-250* standards that list and classify every conceivable and unthinkable aspect of software quality, and even define a methodology for evaluating them (SQuaRE).. True, this technique is so vague that after reading it , the number of suicides grows , more questions remain than before)) In the classification itself, most of the top-level aspects end in "ility" - Testab ility , Reliab ility , Portab ility , etc. .d. - hence the name.
However, if there is a requirement, QA should at least dodge on the navel, but find an opportunity to check / confirm whether it is fulfilled or not ... and there really are such opportunities. Only now they can be called "testing" rather conditionally. Rather, we are talking about methods for analyzing the seemingly subjective characteristics of software quality based on its objective characteristics - from the opinions of independent experts conducting audits (architecture, development processes and quality management systems in the enterprise), and up to the results of a structural analysis of the architecture and static/dynamic code analysis (as an example of the latter approach: SQALE ).