4. Types of Testing

Manual Testing

Definition: Testing conducted manually by humans without using automated scripts or tools. When to Use:

• UI testing, exploratory testing, early-stage projects
• One-time or rarely repeated tests Pros:
• Human intuition, flexibility
• Better for UI/UX validation Cons:
• Time-consuming
• Not scalable for repetitive tasks

Automation Testing

Definition: Using scripts or tools to execute tests automatically. When to Use:

• Regression, performance, data-driven tests
• Repetitive or time-consuming tests Common Tools: Selenium, Cypress, JUnit, TestNG, Postman (API), JMeter (Performance) Pros:
• Faster execution, reusable scripts
• High accuracy, better coverage Cons:
• Requires initial setup and scripting skills
• Not ideal for frequently changing UI

In this chunk, we differentiate between two main types of testing: manual testing and automation testing. Manual testing is where a human tester conducts tests without any tools or scripts, making it suitable for tasks requiring human judgment such as UI/UX validation. It is ideal for early-stage projects or tests that are infrequent. However, it can be time-consuming and not feasible for repetitive tasks.

On the other hand, automation testing employs scripts and tools to automate the execution of tests. This method is well-suited for regression and performance testing, as it allows for faster execution of repetitive tasks with high accuracy. However, it requires technical skills for setup and may not adapt well to frequently changing user interfaces.

Think of manual testing as a chef who prepares a dish from scratch. While they can create a unique taste and adjust the recipe based on their intuition, it takes time and effort. Conversely, automation testing is like using a high-tech kitchen gadget that can mix ingredients and cook automatically. While it speeds up the process and maintains consistency, the gadget needs to be set up correctly and may not adapt well to every recipe change.

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)

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

This chunk introduces two major categories of testing: functional and non-functional testing. Functional testing checks the core functionalities of the system, ensuring that it behaves as expected under various scenarios. It covers different types, such as unit testing and user acceptance testing, assessing specific functions like login and payments.

In contrast, non-functional testing focuses on how well the system performs, assessing aspects such as speed and security. This type includes performance and usability tests to see how the system behaves under stress or how accessible it is to different users.

Imagine functional testing as a vehicle inspection where you check if the car starts, the lights work, and the brakes function correctly. Non-functional testing, however, is like taking that car for a test drive to see how smoothly it accelerates, handles sharp turns, or how comfortable it is for passengers. Both are crucial, but they focus on different aspects of the vehicle.

Regression Testing

Purpose: Verify that new changes haven’t broken existing functionality. When: After every code change, bug fix, or release Tools: Selenium, TestNG, QTP

Smoke Testing

Purpose: A quick set of tests to ensure the core system is stable enough for further testing. Example: Can users log in? Can the homepage load? Analogy: “Does the build smoke when turned on?”

Sanity Testing

Purpose: A focused test to check if a specific function or bug fix works. Example: A defect in the cart page is fixed → test the cart flow only Note: Sanity = “Are we sane to proceed with deeper testing?”

UAT (User Acceptance Testing)

Purpose: Ensure the system meets business needs and is ready for production. Performed By: Business users, stakeholders, sometimes Business Analysts Focus Areas:

• Real-world workflows
• Usability and behavior
• Business rule validation

Performance Testing

Purpose: Measure how the system behaves under load or stress. Subtypes:

• Load Testing: Normal expected user load
• Stress Testing: Beyond normal limits
• Spike Testing: Sudden increase in load
• Soak Testing: Sustained usage over time Tools: Apache JMeter, LoadRunner, Gatling

In this segment, we list some common types of testing encountered in QA processes. Regression testing ensures that changes to the code do not disrupt existing features, performed after any updates. Smoke testing provides a preliminary check to see if critical functionalities are working before further tests are conducted, likened to ensuring a device doesn’t smoke when powered on.

Sanity testing is narrower in focus, confirming that specific fixes are sound before deeper testing proceeds. User Acceptance Testing (UAT) is a pivotal examination to ensure the system fulfills the business requirements and is ready for market introduction, involving actual users or stakeholders. Performance testing assesses the system under various loads to ensure that it can handle real-world usage effectively.

Consider regression testing as checking if a newly painted wall still has no cracks before painting another layer. Smoke testing can be likened to checking if the lights turn on and the engine starts before taking a long trip. Sanity testing is similar to quickly checking if your recently repaired phone can make calls before further testing its other features. UAT is like getting feedback from users who will drive the car to ensure it meets their needs, while performance testing is like stress-testing the engine by driving at high speeds or on steep roads to ensure it doesn’t overheat.

Final Takeaways

• Choose testing type based on context, criticality, and frequency
• Manual and automation complement each other
• Functional testing verifies what the app does, non-functional testing verifies how well
• QA should align testing goals with business and technical priorities

“There’s no one-size-fits-all in testing—choose the right test at the right time for the right outcome.”

This final chunk summarizes the key points of the section on testing types. It emphasizes that the choice of testing should depend on various factors such as the project's context, how critical particular aspects are, and how often tests need to be performed. It underscores that manual and automated testing strategies can work together effectively and that QA should align testing with both business needs and technical requirements to achieve optimal results.

Think about selecting the right tool for a home improvement project. Just as you wouldn't use a hammer to tighten a screw, in testing, you need to choose the appropriate type of testing based on the specific requirements of your project—whether it demands the hands-on approach of manual testing or the efficiency of automation. This ensures the best possible outcome and guarantees the quality of the final product.

--