Service Description: Non-Functional Testing

Making sure non-functional does not mean "none"

Of all the testing disciplines, non-functional testing can appear to be the hardest to understand and manage from a customer's perspective. The name, non-functional testing, is confusing. Who but IT people would give something a name which it is not? If it's not functional, what IS it?

Functional requirements refer to WHAT is built, non-functional requirements relate to HOW that functionality is delivered to the end user. So, you could regard non-functional testing as a way to answer some straightforward questions:

  • Is it fast (enough)?
  • Is it reliable?
  • Is it secure?
  • Is is usable (by typical users)?
  • and so on.

The non-functional test techniques include Performance/Stress/Load, Security, Reliability, Usability, Accessibility, Recovery/Disaster Recovery, Maintainability, Compatibility and Installability. You can see definitions of these various types of test in our Glossary of Testing Terms.

Get in touch with us and we'll arrange a meeting to discuss Non-Functional Testing, what it means, what can go wrong, and how we can help you.

Business Story Pocketbook

The Business Story Method is supported by and largely documented in a book called "The Business Story Pocketbook" which is available for FREE DOWNLOAD or can be purchased from Gerrard Consulting (or other good booksellers).

The Business Story Pocketbook


Download or Buy the Business Story Pocketbook

Testing Axioms and Pocketbook

The Testing Axioms identify the critical thinking processes for testing. As a set of context-neutral rules they also provide a universal testing framework.

The Test Axioms are defined in The Tester's Pocketbook. You can see the axioms online here: testaxioms.com.

The Tester's Pocketbook


Buy The Tester's Pocketbook here

PGtwitterfeed