4.2. Functional vs Non-Functional Testing

🔹 Functional Testing Definition: Verifies what the system does—its business logic and expected outputs. Examples: ● Login functionality ● Form submissions ● Payment processing Types Included: ● Unit Testing ● Integration Testing ● System Testing ● User Acceptance Testing (UAT)

Functional testing is designed to evaluate the specific functionalities of a system by checking if the outputs meet the expected requirements. It focuses on what the system is supposed to do—essentially validating the business logic behind the application. For instance, if an application allows users to log in using their credentials, functional testing would confirm that users can successfully log in and that the application correctly handles both valid and invalid input scenarios. The types of functional testing include Unit Testing (testing smallest parts of the code), Integration Testing (checking how different pieces of the application work together), System Testing (testing the entire application as a whole), and User Acceptance Testing (UAT), which verifies that the system meets the needs of the user.

Think of functional testing like a cooking competition. The judges (testers) will taste the final dish (the completed application) to see if it meets the recipe specifications (requirements). If the dish tastes good (functions as expected) and meets the specifications (requirements), the cook (developer) has succeeded. If it doesn't taste right (produces errors), then adjustments need to be made.

🔹 Non-Functional Testing Definition: Verifies how the system performs, focusing on attributes like speed, security, usability. Examples: ● Page load speed ● System under stress ● Accessibility for users with disabilities Types Included: ● Performance Testing ● Load Testing ● Security Testing ● Usability Testing ● Compatibility Testing

Non-functional testing evaluates how well the system performs under various conditions rather than what it does. It focuses on more qualitative aspects like performance, security, usability, and compatibility with other systems. For example, non-functional testing might assess how quickly a website loads under high traffic (performance testing), how safe it is from external attacks (security testing), or how easy it is for users with disabilities to navigate the interface (usability testing). This type of testing often includes various approaches, such as Performance Testing (measuring speed and responsiveness), Load Testing (checking how the system handles expected user loads), and Compatibility Testing (ensuring the system works across various devices and environments).

Imagine non-functional testing as evaluating a car not just for its ability to drive (functional) but also for how fast it goes (performance), how it handles rough terrain (usability), or how it fares in a crash (security). Just like a car needs to be safe and efficient, software needs to perform well and be secure to be successful.

Types Included: ● Unit Testing ● Integration Testing ● System Testing ● User Acceptance Testing (UAT)

There are several specific types of functional testing, each serving a distinct purpose: Unit Testing focuses on the smallest testable parts of the application (usually individual functions or methods), ensuring each works correctly in isolation. Integration Testing examines how different modules work together after unit tests; it assesses data exchange between units. System Testing involves testing the complete application in an environment that mimics production to evaluate end-to-end system specifications. Lastly, User Acceptance Testing (UAT) is performed by end-users to determine if the application meets their business needs and is ready for deployment.

You can think of these types of testing like preparing a new restaurant for opening. Unit Testing is like each chef practicing their signature dish (testing individual components), Integration Testing is checking how the courses flow from the kitchen to the dining area (seeing if everything works together), System Testing is running a full dinner service to see if the restaurant functions well as a whole, and UAT is inviting customers to taste the food and give feedback before the grand opening.

Types Included: ● Performance Testing ● Load Testing ● Security Testing ● Usability Testing ● Compatibility Testing

Non-functional testing encompasses multiple types, each directed at different performance parameters. Performance Testing evaluates the application's response times, throughput, and resource usage. Load Testing specifically assesses how the system behaves under normal and peak load conditions, while Security Testing looks for vulnerabilities and ensures data protection. Usability Testing gathers user feedback regarding the system’s intuitiveness and ease of use, and Compatibility Testing ensures that the application works across various operating systems, browsers, and devices. These testing types can all be critical in ensuring that users have a positive experience while interacting with the application.

Consider non-functional testing like preparing for a marathon. Performance Testing is like training to run a certain distance at a set speed (how quickly the application can respond). Load Testing assesses how many runners can participate (how many users can access the system at once). Security Testing is making sure each runner is safe on the path (ensuring data integrity). Usability Testing checks if the route is easy to navigate for everyone, and Compatibility Testing ensures runners can compete in various weather conditions (the application functions on different platforms).

--