Functional & Non-Functional Testing

Functional Testing: Testing the application against business requirements. Functional testing is done using the functional specifications provided by the client or by using the design specifications like use cases provided by the design team.
Testing the behavior of the application, Here testing is done based on the external behavior of the application , Internal code is not mattered.
Ex: Suppose if we click a "Submit” button after giving all the details in a relevant page , is it getting saved ? Or is it giving the relevant error message, this is an ex for Functional Testing

Functional Testing covers:
• Unit Testing
• Smoke Testing / Sanity Testing
• Integration Testing (Top Down, Bottom up Testing)
• Interface & Usability Testing
• System Testing
• Regression Testing
• Pre User Acceptance Testing (Alpha & Beta)
• User Acceptance Testing
• White Box & Black Box Testing
• Globalization & Localization Testing

Non-Functional Testing: Testing the application against client's and performance requirement. Non -Functioning testing is done based on the requirements and test scenarios defined by the client.
To verify that the system will work in production and will provide consistent and predictable level of service. It includes measuring resource utilization, performing high volume stress tests, testing system break points and testing performance bottlenecks

Non-Functional Testing covers:
• Load and Performance Testing
• Ergonomics Testing
• Stress & Volume Testing
• Compatibility & Migration Testing
• Data Conversion Testing
• Security / Penetration Testing
• Operational Readiness Testing
• Installation Testing
• Security Testing
• (Application Security, Network Security, System Security)