Functional Testing
- It focuses on testing the functionality of the software or system.
- Verifies whether the software meets the functional requirements.
- It involves testing the features and functionalities of the software, such as input/output, error handling, and user interface.
- Tests are typically conducted using test cases or scenarios that validate the functional requirements.
- It can be performed manually or using automated testing tools.
- It was done after unit testing and integration testing and before system testing.
Non-Functional Testing
- It focuses on testing the system's or software's non-functional components.
- Checks to see if the software satisfies the non-functional requirements, including performance, security, usability, reliability, and compatibility.
- It involves putting the software's quality characteristics, including response time, scalability, availability, and maintainability, to the test.
- Several testing methods, including load testing, stress testing, security testing, and usability testing, are used.
- Specialist testing techniques and frameworks are frequently needed to measure and assess non-functional requirements.
- Many development lifecycle stages, including design, deployment, and maintenance, can be completed.
Examples of Functional testing are
- Unit Testing
- Smoke Testing
- Sanity Testing
- Integration Testing
- White box testing
- Black Box testing
- User Acceptance testing
- Regression Testing
Examples of Non-functional testing are
- Performance Testing
- Load Testing
- Volume Testing
- Stress Testing
- Security Testing
- Installation Testing
- Penetration Testing
- Compatibility Testing
- Migration Testing
Top comments (0)