Definition of Non-functional testing
I keep seeing the term "functional and non-functional" testing in requirements for automation work.
What does this mean?
Does non-functional mean performance, cosmetic and other things that are not functional or does it mean something specific?
Functional generally relates to user requirements.
Non functional tends to be all the '...ity' testing.
Ex: Security, Reliability, Scalability, Maintainability, etc...
Perceived that non-functional testing as performance testing though not certain on this, Real time definition would be appreciated.
You have the right idea. (Although it's always best to check with whoever wrote the requirements, since definitions tend to be very squishy.)
Originally Posted by bklabel1
Just to clarify..
So there are expectations made explicit in the requirements, functional requirements. What the user sees, how it works.
Then there are expectations of the software that are there even though it's not specifically spelled out. Scaleability/Performance, Security, Reliability, etc..
That's what I mean about ...ity testing. Most of those adjectives that describe what the software should be like, have an ..ity at the end. Of course there are some you might find hard to phrase, like, SARBOX compliance for example in the finance industry.
Non-functional testing refers to the testing the software for the requirements which are not specific and functional of that software. Regardless, testing the other requirements which are not operational functions of that application.
Functionality testing is performed to verify that a software application performs and functions correctly according to design specifications. It falls in to two categories:
1. Positive functional testing: - This testing carry exercising the application’s functions with valid input and also verifying that the outputs are correct.
2. Negative functional testing: - This testing involves exercising application functionality using a combination of invalid inputs, some unexpected operating conditions and by some other “out-of-bounds” scenarios.
The non Functional Testing is the type of testing done against the non functional requirements. Non-functional requirements tend to be those that reflect the quality of the product, particularly in the context of the suitability perspective of its users. It can be started after the completion of Functional Testing. The non functional tests can be effective by using testing tools.
The testing of software attributes which are not related to any specific function or user action like performance, scalability, security or behavior of application under certain constraints. Non functional testing has a great influence on customer and user satisfaction with the product.
Following testing should consider in non functional testing types:
- Baseline testing
- Compatibility testing
- Compliance testing
- Configuration Testing
- Documentation testing
- Installation Testing
- Load testing
- Localization testing and Internationalization testing
- Performance testing
- Security testing
- Stress testing
Further you might also like to get more information of different types of manual testing:
“Quality That Creates Value”
QASource delivers your own experienced QA team, a comprehensive QA infrastructure focused on efficiency and excellence, and a new, multi-million-dollar lab.
Functional - if the product is ready with the purpose intended, the business requirement met for the user to use the product
Non-functional - how effective the product is working like the response time, concurrent users etc
Security also comes under functional btw
No functional testing refer to all test activity which is no related to the funcionality of the apps undertest. Non fuct.test i.e. hardware, performace, etc.
I appreciate you writing this explanation.
When in Florida, Don't Tampa with the code. I made this up.