Non-Functional Types of Testing
Non-functional software testing types are related to non-functional requirements (performance requirement and client’s expectations) and help to evaluate the attributes of the system such as robustness, memory leaks, reliability, usability, robustness of the system, etc. Non-functional testing refers to the aspects of the software that will never be addressed by functional testing. It specifies how the system operates, performing checks on wider quality concerns, rather than on the specific behavior of this system.
There are many subtypes of non-functional testing
User interface testing is the process of assessing the graphical user interface to ensure it is in compliance with its written specification. At that it is a critical part of SDLC. This testing technique aids in identifying presence of defects / bugs in a software product under test by using GUI. User interface testing is used to evaluate controls (design elements) such as buttons, text boxes, icons, menus, lists, font size, labels, layouts, text captions, etc, verifying that they are present and located in the right place.
The approaches of UI testing are: manual based testing, model-based testing, record and reply.
The most popular user interface testing tools and frameworks are: Jubula, FitNesse, Coded UI, iMacros, LoadUI.
User experience-based testing is aimed at checking how users feel about interaction with the product or service of the company. It helps to understand what customers need and what they value and also their capabilities and limitations. Actually, UX is much more than just a visual interface of your product / software. It includes:
- impressions that a client receives from the interaction with your product or service;
- process a client should go through to get familiar with your product or service;
- a sequence of actions performed by a client when interacting with the app though its graphical user interface.
The most popular UX testing tools and frameworks are: Usabilla, Visual Web Optimizer, Omnigraffle, UXPin, Crazy Egg.
Storage testing verifies whether the app under test stores and reads the adequate data files in the appropriate directories and if there is enough space to prevent unexpected termination owing to insufficient disk space. This technique helps to find out whether the app consumes more memory than expected because lack of free hard drive space may lead to significant downtime.
Storage testing tools: Iometer, HCIbench, Diskspd Utility.
Want to obtain exhaustive info on non-functional testing? Eager to know its other types? If so, SQA consulting will be of great use to you!