Non-Functional Testing Too is important in QA Process Majority of the testers will focus more on testing the product against client requirements – which we mention as Functional Testing and pay less attention to non-functional testing. Non-functional requirements often play a significant role in differentiating between a product that is well received by customers vs one that may not do well in the market place. Some of the key non-functional requirements include Usability, Performance, Security, and Interoperability & Compatibility. To be more precise, Functional requirements define what a system will do while Non-functional requirements describe how the system will do it. Non-functional requirements characterize the behavior that is required in functional requirements There are some situations which really makes the QA users and project managers to think about importance of non-functional testing for their products. A few of them would be Multi-user application that has tones of great functional features but simply crawls or frequently hangs up when several users try to use the system A web application that works best only in a limited set of browser types and versions on limited platforms and unfortunately there are users using and comfortable on other versions of browsers and platforms An application that has sensitive data but is fairly easily susceptible to security breaches and exposure of sensitive information Product containing excellent features, but vague for real time usage Actual Users because of poor user manual documentation Project is fully complete and deployed in production systems but users could not able to access the system In the above scenarios, the tester role is not only limited to test the product against the client specification, but also to verify non-functional requirements. Non-functional risks need to be evaluated and considered during project planning. During requirements phase, both functional and non-functional requirements need to be spelt out and considered by both development and testing teams. The following testing can be considered as a part of non-functional testing and should be performed for a successful delivery of a product and to help the marketing team for a better sale
Visit IVESIA’S WEBSITE Follow us at LINKEDIN and TWITTER
Perform Load Testing to see, how the product behaves under heavy stress/Load. Try to load the system with many users and complicated actions Calculate the System performance and Response time and ensure product has good performance even during network traffic Carry out installation testing and verify the product is easy to install without technical expert intervention. Even if it requires, make sure it needs minimal external guidance Perform Stress and Volume testing to product Concentrate on compatibility testing and ensure product behaves consistent in all most widely used browsers and operating system Check for Security Testing which includes Application Security, Network Security, System Security Give importance to documentation testing and verify User Manual Guide, Release notes are reflecting latest updates and highlights
Visit IVESIA’S WEBSITE Follow us at LINKEDIN and TWITTER